Unmanned device interaction methods and systems

ABSTRACT

Structures and protocols are presented for configuring an unmanned aerial device to participate in the performance of tasks, for using data resulting from such a configuration or performance, or for facilitating other interactions with such devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)). All subject matter ofthe Related Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications,including any priority claims, is incorporated herein by reference tothe extent such subject matter is not inconsistent herewith.

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. application Ser.No. 13/551,266, U.S. application Ser. No. 13/551,287, U.S. applicationSer. No. 13/551,301, U.S. application Ser. No. 13/551,320, and U.S.application Ser. No. 13/551,334, each entitled UNMANNED DEVICEUTILIZATION METHODS AND SYSTEMS, naming Royce A. Levien, Richard T.Lord, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., and LowellL. Wood, Jr., as inventors, filed 17 Jul. 2012, each of which iscurrently co-pending or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.For purposes of the USPTO extra-statutory requirements, the presentapplication likewise constitutes a continuation-in-part of {AttorneyDocket Nos. 0212-035-006, 0212-035-008, 0212-035-009, 0212-035-010,0212-035-011, 0212-035-012}, each entitled UNMANNED DEVICE INTERACTIONMETHODS AND SYSTEMS, naming Royce A. Levien, Richard T. Lord, Robert W.Lord, Mark A. Malamud, John D. Rinaldo, Jr., and Lowell L. Wood, Jr., asinventors, filed on even date herewith, each of which is currentlyco-pending or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. application Ser. No.13/551,266, U.S. application Ser. No. 13/551,287, U.S. application Ser.No. 13/551,301, U.S. application Ser. No. 13/551,320, and U.S.application Ser. No. 13/551,334, each entitled UNMANNED DEVICEUTILIZATION METHODS AND SYSTEMS, naming Royce A. Levien, Richard T.Lord, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., and LowellL. Wood, Jr., as inventors, filed 17 Jul. 2012, each of which was filedwithin the twelve months preceding the filing date of the presentapplication or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date. For purposesof the USPTO extra-statutory requirements, the present applicationlikewise claims benefit of priority of {Attorney Docket Nos.0212-035-006, 0212-035-008, 0212-035-009, 0212-035-010, 0212-035-011,0212-035-012}, each entitled UNMANNED DEVICE INTERACTION METHODS ANDSYSTEMS, naming Royce A. Levien, Richard T. Lord, Robert W. Lord, MarkA. Malamud, John D. Rinaldo, Jr., and Lowell L. Wood, Jr., as inventors,filed on even date herewith, each of which was filed within the twelvemonths preceding the filing date of the present application or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The present Applicant Entity(hereinafter “Applicant”) has provided above a specific reference to theapplication(s) from which priority is being claimed as recited bystatute. Applicant understands that the statute is unambiguous in itsspecific reference language and does not require either a serial numberor any characterization, such as “continuation” or“continuation-in-part,” for claiming priority to U.S. patentapplications. Notwithstanding the foregoing, Applicant understands thatthe USPTO's computer programs have certain data entry requirements, andhence Applicant has provided designation(s) of a relationship betweenthe present application and its parent application(s) as set forthabove, but expressly points out that such designation(s) are not to beconstrued in any way as any type of commentary and/or admission as towhether or not the present application contains any new matter inaddition to the matter of its parent application(s).

BACKGROUND

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for the massively complex computationalmachines or other means. As discussed in detail below, theoperational/functional language must be read in its proper technologicalcontext, i.e., as concrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to the human mind. The distillationalso allows one of skill in the art to adapt the operational/functionaldescription of the technology across many different specific vendors'hardware configurations or platforms, without being limited to specificvendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail in the followingparagraphs, these logical operations/functions are not representationsof abstract ideas, but rather representative of static or sequencedspecifications of various hardware elements. Differently stated, unlesscontext dictates otherwise, the logical operations/functions will beunderstood by those of skill in the art to be representative of staticor sequenced specifications of various hardware elements. This is truebecause tools available to one of skill in the art to implementtechnical disclosures set forth in operational/functional formats—toolsin the form of a high-level programming language (e.g., C, java, visualbasic), etc.), or tools in the form of Very high speed HardwareDescription Language (“VHDL,” which is a language that uses text todescribe logic circuits)—are generators of static or sequencedspecifications of various hardware configurations. This fact issometimes obscured by the broad term “software,” but, as shown by thefollowing explanation, those skilled in the art understand that what istermed “software” is a shorthand for a massively complexinterchaining/specification of ordered-matter elements. The term“ordered-matter elements” may refer to physical components ofcomputation, such as assemblies of electronic logic gates, molecularcomputing logic constituents, quantum computing mechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. See, e.g., Wikipedia, High-level programming language,http://en.wikipedia.org/wiki/High-level_programming_language (as of Jun.5, 2012, 21:00 GMT). In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages. See, e.g., Wikipedia, Natural language,http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00GMT).

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct.”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood in the human mind). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices), molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of Boolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT).

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute a shorthand that specifies theapplication of specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configuration, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). See, e.g.,Wikipedia, Instructions per second,http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5,2012, 21:04 GMT).

Thus, programs written in machine language—which may be tens of millionsof machine language instructions long—are incomprehensible. In view ofthis, early assembly languages were developed that used mnemonic codesto refer to machine language instructions, rather than using the machinelanguage instructions' numeric values directly (e.g., for performing amultiplication operation, programmers coded the abbreviation “mult,”which represents the binary number “011000” in MIPS machine code). Whileassembly languages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thathumanly useful, tangible, and concrete work is done. For example, asindicated above, such machine language—the compiled version of thehigher-level language—functions as a technical specification whichselects out hardware logic gates, specifies voltage levels, voltagetransition timings, etc., such that the humanly useful work isaccomplished by the hardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality representative of logic(s), or (d) virtually anycombination of the foregoing. Indeed, any physical object which has astable, measurable, and changeable state may be used to construct amachine based on the above technical description. Charles Babbage, forexample, constructed the first computer out of wood and powered bycranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language simply cannot be taken as anindication that such functional/operational technical descriptions areabstract ideas, or mere expressions of abstract ideas. In fact, asoutlined herein, in the technological arts this is simply not true. Whenviewed through the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

SUMMARY

In one or more various aspects, a method includes but is not limited toobtaining a descriptor of a first entity operating a first unmannedaerial device; obtaining an operatorship criterion; and signaling adecision whether or not to impede the first unmanned aerial deviceentering a particular region as an automatic and conditional result ofapplying the operatorship criterion to the descriptor of the firstentity operating the first unmanned aerial device. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining a descriptor of afirst entity operating a first unmanned aerial device; circuitry forobtaining an operatorship criterion; and circuitry for signaling adecision whether or not to impede the first unmanned aerial deviceentering a particular region as an automatic and conditional result ofapplying the operatorship criterion to the descriptor of the firstentity operating the first unmanned aerial device. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtaininga descriptor of a first entity operating a first unmanned aerial device;obtaining an operatorship criterion; and signaling a decision whether ornot to impede the first unmanned aerial device entering a particularregion as an automatic and conditional result of applying theoperatorship criterion to the descriptor of the first entity operatingthe first unmanned aerial device. In addition to the foregoing, othercomputer program products are described in the claims, drawings, andtext forming a part of the disclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining a descriptor of a firstentity operating a first unmanned aerial device; obtaining anoperatorship criterion; and signaling a decision whether or not toimpede the first unmanned aerial device entering a particular region asan automatic and conditional result of applying the operatorshipcriterion to the descriptor of the first entity operating the firstunmanned aerial device. In addition to the foregoing, other computerarchitecture details are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining a descriptor of a first entityoperating a first unmanned aerial device; obtaining an operatorshipcriterion; and signaling a decision whether or not to impede the firstunmanned aerial device entering a particular region as an automatic andconditional result of applying the operatorship criterion to thedescriptor of the first entity operating the first unmanned aerialdevice. In addition to the foregoing, other hardware aspects aredescribed in the claims, drawings, and text forming a part of thedisclosure set forth herein.

In one or more various aspects, a method includes but is not limited todetecting a first unmanned aerial device being within a vicinity of aportal; obtaining an indication of an identity of the first unmannedaerial device; and signaling a decision whether or not to allow anactuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal. Inaddition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for detecting a first unmannedaerial device being within a vicinity of a portal; circuitry forobtaining an indication of an identity of the first unmanned aerialdevice; and circuitry for signaling a decision whether or not to allowan actuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, detectinga first unmanned aerial device being within a vicinity of a portal;obtaining an indication of an identity of the first unmanned aerialdevice; and signaling a decision whether or not to allow an actuator toobstruct the portal partly based on the indication of the identity ofthe first unmanned aerial device and partly based on the first unmannedaerial device being within the vicinity of the portal. In addition tothe foregoing, other computer program products are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, detecting a first unmanned aerialdevice being within a vicinity of a portal; obtaining an indication ofan identity of the first unmanned aerial device; and signaling adecision whether or not to allow an actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal. In addition to the foregoing, othercomputer architecture details are described in the claims, drawings, andtext forming a part of the disclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, detecting a first unmanned aerial device beingwithin a vicinity of a portal; obtaining an indication of an identity ofthe first unmanned aerial device; and signaling a decision whether ornot to allow an actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal. In addition to the foregoing, other hardwareaspects are described in the claims, drawings, and text forming a partof the disclosure set forth herein.

In one or more various aspects, a method includes but is not limited toobtaining first data including optical data from a vicinity of areference surface in contact with a first unmanned aerial device;signaling a decision as an automatic and conditional response to theapplication of a first recognition criterion to the optical data fromthe vicinity of the reference surface in contact with the first unmannedaerial device whether or not to cause the first unmanned aerial deviceto be disengaged from the reference surface; and signaling a decision asan automatic and conditional response to the application of the firstrecognition criterion to the optical data from the vicinity of thereference surface whether or not to cause the first unmanned aerialdevice to obtain second data with the first unmanned aerial devicedisengaged from the reference surface. In addition to the foregoing,other method aspects are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining first dataincluding optical data from a vicinity of a reference surface in contactwith a first unmanned aerial device; circuitry for signaling a decisionas an automatic and conditional response to the application of a firstrecognition criterion to the optical data from the vicinity of thereference surface in contact with the first unmanned aerial devicewhether or not to cause the first unmanned aerial device to bedisengaged from the reference surface; and circuitry for signaling adecision as an automatic and conditional response to the application ofthe first recognition criterion to the optical data from the vicinity ofthe reference surface whether or not to cause the first unmanned aerialdevice to obtain second data with the first unmanned aerial devicedisengaged from the reference surface. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtainingfirst data including optical data from a vicinity of a reference surfacein contact with a first unmanned aerial device; signaling a decision asan automatic and conditional response to the application of a firstrecognition criterion to the optical data from the vicinity of thereference surface in contact with the first unmanned aerial devicewhether or not to cause the first unmanned aerial device to bedisengaged from the reference surface; and signaling a decision as anautomatic and conditional response to the application of the firstrecognition criterion to the optical data from the vicinity of thereference surface whether or not to cause the first unmanned aerialdevice to obtain second data with the first unmanned aerial devicedisengaged from the reference surface. In addition to the foregoing,other computer program products are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining first data including opticaldata from a vicinity of a reference surface in contact with a firstunmanned aerial device; signaling a decision as an automatic andconditional response to the application of a first recognition criterionto the optical data from the vicinity of the reference surface incontact with the first unmanned aerial device whether or not to causethe first unmanned aerial device to be disengaged from the referencesurface; and signaling a decision as an automatic and conditionalresponse to the application of the first recognition criterion to theoptical data from the vicinity of the reference surface whether or notto cause the first unmanned aerial device to obtain second data with thefirst unmanned aerial device disengaged from the reference surface. Inaddition to the foregoing, other computer architecture details aredescribed in the claims, drawings, and text forming a part of thedisclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining first data including optical data froma vicinity of a reference surface in contact with a first unmannedaerial device; signaling a decision as an automatic and conditionalresponse to the application of a first recognition criterion to theoptical data from the vicinity of the reference surface in contact withthe first unmanned aerial device whether or not to cause the firstunmanned aerial device to be disengaged from the reference surface; andsignaling a decision as an automatic and conditional response to theapplication of the first recognition criterion to the optical data fromthe vicinity of the reference surface whether or not to cause the firstunmanned aerial device to obtain second data with the first unmannedaerial device disengaged from the reference surface. In addition to theforegoing, other hardware aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, a method includes but is not limited toobtaining operator input from an operator of a first unmanned aerialdevice as an earlier input component; obtaining environmental sensorinput from a vicinity of the first unmanned aerial device as a laterinput component; and signaling a decision without regard to any otheroperator input whether or not to launch the first unmanned aerial devicepartly based on the operator input from the operator of the firstunmanned aerial device obtained as the earlier input component andpartly based on the environmental sensor input from the vicinity of thefirst unmanned aerial device obtained as the later input component. Inaddition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining operator inputfrom an operator of a first unmanned aerial device as an earlier inputcomponent; circuitry for obtaining environmental sensor input from avicinity of the first unmanned aerial device as a later input component;and circuitry for signaling a decision without regard to any otheroperator input whether or not to launch the first unmanned aerial devicepartly based on the operator input from the operator of the firstunmanned aerial device obtained as the earlier input component andpartly based on the environmental sensor input from the vicinity of thefirst unmanned aerial device obtained as the later input component. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtainingoperator input from an operator of a first unmanned aerial device as anearlier input component; obtaining environmental sensor input from avicinity of the first unmanned aerial device as a later input component;and signaling a decision without regard to any other operator inputwhether or not to launch the first unmanned aerial device partly basedon the operator input from the operator of the first unmanned aerialdevice obtained as the earlier input component and partly based on theenvironmental sensor input from the vicinity of the first unmannedaerial device obtained as the later input component. In addition to theforegoing, other computer program products are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining operator input from anoperator of a first unmanned aerial device as an earlier inputcomponent; obtaining environmental sensor input from a vicinity of thefirst unmanned aerial device as a later input component; and signaling adecision without regard to any other operator input whether or not tolaunch the first unmanned aerial device partly based on the operatorinput from the operator of the first unmanned aerial device obtained asthe earlier input component and partly based on the environmental sensorinput from the vicinity of the first unmanned aerial device obtained asthe later input component. In addition to the foregoing, other computerarchitecture details are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining operator input from an operator of afirst unmanned aerial device as an earlier input component; obtainingenvironmental sensor input from a vicinity of the first unmanned aerialdevice as a later input component; and signaling a decision withoutregard to any other operator input whether or not to launch the firstunmanned aerial device partly based on the operator input from theoperator of the first unmanned aerial device obtained as the earlierinput component and partly based on the environmental sensor input fromthe vicinity of the first unmanned aerial device obtained as the laterinput component. In addition to the foregoing, other hardware aspectsare described in the claims, drawings, and text forming a part of thedisclosure set forth herein.

In one or more various aspects, a method includes but is not limited toobtaining first data including an X-ordinate of a first location and aY-ordinate of the first location indicating a first entity moving fromthe first location to a second location; obtaining second dataindicative of a device-detectable energy signature path having existedbetween a second entity and the first location; obtaining third dataindicative of no device-detectable energy signature path having existedbetween the second entity and the second location; and causing the firstentity to travel from a third location toward the first location partlybased on the X-ordinate and partly based on the Y-ordinate and partlybased on the second data indicative of the device-detectable energysignature path having existed between the second entity and the firstlocation and partly based on the third data indicative of nodevice-detectable energy signature path having existed between thesecond entity and the second location. In addition to the foregoing,other method aspects are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining first dataincluding an X-ordinate of a first location and a Y-ordinate of thefirst location indicating a first entity moving from the first locationto a second location; circuitry for obtaining second data indicative ofa device-detectable energy signature path having existed between asecond entity and the first location; circuitry for obtaining third dataindicative of no device-detectable energy signature path having existedbetween the second entity and the second location; and circuitry forcausing the first entity to travel from a third location toward thefirst location partly based on the X-ordinate and partly based on theY-ordinate and partly based on the second data indicative of thedevice-detectable energy signature path having existed between thesecond entity and the first location and partly based on the third dataindicative of no device-detectable energy signature path having existedbetween the second entity and the second location. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtainingfirst data including an X-ordinate of a first location and a Y-ordinateof the first location indicating a first entity moving from the firstlocation to a second location; obtaining second data indicative of adevice-detectable energy signature path having existed between a secondentity and the first location; obtaining third data indicative of nodevice-detectable energy signature path having existed between thesecond entity and the second location; and causing the first entity totravel from a third location toward the first location partly based onthe X-ordinate and partly based on the Y-ordinate and partly based onthe second data indicative of the device-detectable energy signaturepath having existed between the second entity and the first location andpartly based on the third data indicative of no device-detectable energysignature path having existed between the second entity and the secondlocation. In addition to the foregoing, other computer program productsare described in the claims, drawings, and text forming a part of thedisclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining first data including anX-ordinate of a first location and a Y-ordinate of the first locationindicating a first entity moving from the first location to a secondlocation; obtaining second data indicative of a device-detectable energysignature path having existed between a second entity and the firstlocation; obtaining third data indicative of no device-detectable energysignature path having existed between the second entity and the secondlocation; and causing the first entity to travel from a third locationtoward the first location partly based on the X-ordinate and partlybased on the Y-ordinate and partly based on the second data indicativeof the device-detectable energy signature path having existed betweenthe second entity and the first location and partly based on the thirddata indicative of no device-detectable energy signature path havingexisted between the second entity and the second location. In additionto the foregoing, other computer architecture details are described inthe claims, drawings, and text forming a part of the disclosure setforth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining first data including an X-ordinate of afirst location and a Y-ordinate of the first location indicating a firstentity moving from the first location to a second location; obtainingsecond data indicative of a device-detectable energy signature pathhaving existed between a second entity and the first location; obtainingthird data indicative of no device-detectable energy signature pathhaving existed between the second entity and the second location; andcausing the first entity to travel from a third location toward thefirst location partly based on the X-ordinate and partly based on theY-ordinate and partly based on the second data indicative of thedevice-detectable energy signature path having existed between thesecond entity and the first location and partly based on the third dataindicative of no device-detectable energy signature path having existedbetween the second entity and the second location. In addition to theforegoing, other hardware aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, a method includes but is not limited toobtaining an indication of a first time interval from when adevice-detectable energy signature path existed between a first entityand a second entity until a reference time and signaling a decisionwhether or not to change an aerial navigation protocol of the firstentity as an automatic and conditional response to a result of comparinga threshold against the indication of the first time interval from whenthe device-detectable energy signature path existed between the firstentity and the second entity until the reference time. In addition tothe foregoing, other method aspects are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indication ofa first time interval from when a device-detectable energy signaturepath existed between a first entity and a second entity until areference time and circuitry for signaling a decision whether or not tochange an aerial navigation protocol of the first entity as an automaticand conditional response to a result of comparing a threshold againstthe indication of the first time interval from when thedevice-detectable energy signature path existed between the first entityand the second entity until the reference time. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtainingan indication of a first time interval from when a device-detectableenergy signature path existed between a first entity and a second entityuntil a reference time and signaling a decision whether or not to changean aerial navigation protocol of the first entity as an automatic andconditional response to a result of comparing a threshold against theindication of the first time interval from when the device-detectableenergy signature path existed between the first entity and the secondentity until the reference time. In addition to the foregoing, othercomputer program products are described in the claims, drawings, andtext forming a part of the disclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining an indication of a first timeinterval from when a device-detectable energy signature path existedbetween a first entity and a second entity until a reference time andsignaling a decision whether or not to change an aerial navigationprotocol of the first entity as an automatic and conditional response toa result of comparing a threshold against the indication of the firsttime interval from when the device-detectable energy signature pathexisted between the first entity and the second entity until thereference time. In addition to the foregoing, other computerarchitecture details are described in the claims, drawings, and textforming a part of the disclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining an indication of a first time intervalfrom when a device-detectable energy signature path existed between afirst entity and a second entity until a reference time and signaling adecision whether or not to change an aerial navigation protocol of thefirst entity as an automatic and conditional response to a result ofcomparing a threshold against the indication of the first time intervalfrom when the device-detectable energy signature path existed betweenthe first entity and the second entity until the reference time. Inaddition to the foregoing, other hardware aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, a method includes but is not limited toobtaining photographic data depicting a first unmanned aerial device;obtaining an indication whether or not the first unmanned aerial devicebehaved anomalously; and signaling a decision whether or not to transmitthe photographic data depicting the first unmanned aerial device as anautomatic and conditional response to the indication whether or not thefirst unmanned aerial device behaved anomalously. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining photographic datadepicting a first unmanned aerial device; circuitry for obtaining anindication whether or not the first unmanned aerial device behavedanomalously; and circuitry for signaling a decision whether or not totransmit the photographic data depicting the first unmanned aerialdevice as an automatic and conditional response to the indicationwhether or not the first unmanned aerial device behaved anomalously. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one aspect, a computer program product comprising an article ofmanufacture bears instructions including, but not limited to, obtainingphotographic data depicting a first unmanned aerial device; obtaining anindication whether or not the first unmanned aerial device behavedanomalously; and signaling a decision whether or not to transmit thephotographic data depicting the first unmanned aerial device as anautomatic and conditional response to the indication whether or not thefirst unmanned aerial device behaved anomalously. In addition to theforegoing, other computer program products are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one aspect, a computer architecture comprising at least one levelincludes, but is not limited to, obtaining photographic data depicting afirst unmanned aerial device; obtaining an indication whether or not thefirst unmanned aerial device behaved anomalously; and signaling adecision whether or not to transmit the photographic data depicting thefirst unmanned aerial device as an automatic and conditional response tothe indication whether or not the first unmanned aerial device behavedanomalously. In addition to the foregoing, other computer architecturedetails are described in the claims, drawings, and text forming a partof the disclosure set forth herein.

In one aspect, a device configured by computational language includes,but is not limited to, obtaining photographic data depicting a firstunmanned aerial device; obtaining an indication whether or not the firstunmanned aerial device behaved anomalously; and signaling a decisionwhether or not to transmit the photographic data depicting the firstunmanned aerial device as an automatic and conditional response to theindication whether or not the first unmanned aerial device behavedanomalously. In addition to the foregoing, other hardware aspects aredescribed in the claims, drawings, and text forming a part of thedisclosure set forth herein.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent by referenceto the detailed description, the corresponding drawings, and/or in theteachings set forth herein

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an exemplary environment featuring a primary unitoperably linked to a network.

FIG. 2 depicts an exemplary environment featuring a user-accessiblekiosk having several bays in which unmanned aerial devices (UAD's) mayreside.

FIG. 3 depicts an exemplary environment featuring an interface devicehaving at least one processor.

FIG. 4 depicts an exemplary environment featuring an event/conditiondetection unit.

FIG. 5 depicts an exemplary environment featuring a UAD in a vicinity ofa destination.

FIG. 6 depicts an exemplary environment featuring a UAD and anotherentity (a car or driver, e.g.) communicating about a resource (parkingspace, e.g.).

FIG. 7 depicts an exemplary environment featuring three pedestrians inone zone, one pedestrian in another zone, and at least one handheld UAD.

FIG. 8 depicts an exemplary environment featuring UAD's operably coupledwith a network.

FIG. 9 depicts an exemplary environment featuring a UAD traveling amongseveral stations.

FIG. 10 depicts an exemplary environment featuring a device (UAD, e.g.)operably coupled with a network via a communication linkage.

FIG. 11 depicts an exemplary environment featuring a secondary unit.

FIG. 12 depicts a physical medium residing in one or more of theabove-described environments.

FIG. 13 depicts a chair, keyboard, and desktop in an office into which aUAD may enter.

FIG. 14 depicts an exemplary environment featuring an article ofmanufacture.

FIG. 15 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 5.

FIG. 16 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 6.

FIG. 17 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 7.

FIG. 18 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 8.

FIG. 19 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 9.

FIG. 20 depicts an exemplary environment featuring a structuralcomponent of a UAD having at least a releasable mechanical linkage to apackage or other cargo module.

FIGS. 21-24 each depicts physical media residing in one or more of theabove-described environments.

FIG. 25 depicts a detection unit usable in one or more of theabove-described environments to detect time intervals or other physicalphenomena.

FIG. 26 depicts a disablement device usable in one or more of theabove-described environments to disable a UAD.

FIG. 27 depicts a stationary structure configured to support orotherwise interact with a UAD.

FIG. 35 depicts an exemplary environment featuring a data handling unit.

FIG. 36 depicts an exemplary environment like that of FIG. 1, featuringa primary unit operably linked to a network.

FIG. 37 depicts an exemplary environment like that of FIG. 11, featuringa secondary unit.

FIG. 28 depicts an exemplary environment featuring two UAD's in avicinity of a house.

FIG. 38 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 28.

FIG. 29 depicts an exemplary environment featuring a UAD in a vicinityof a garage.

FIG. 39 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 29.

FIG. 30 depicts a front view of a structure configured to support aquadcopter-type UAD.

FIG. 40 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 30.

FIG. 31 depicts a side view of the structure of FIG. 30.

FIG. 41 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 31.

FIG. 32 depicts an entity only intermittently able to obtain anindication of another entity, one or both being UAD's.

FIG. 42 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 32.

FIG. 33 depicts entities like those of FIG. 32, one only intermittentlyable to obtain an indication of another due to intervening obstacles.

FIG. 43 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 33.

FIG. 34 depicts an exemplary environment featuring a device configuredto signal a decision whether or not to transmit a depiction of a UAD.

FIG. 44 depicts a high-level logic flow of an operational processdescribed with reference to FIG. 34.

FIG. 45 depicts physical media residing in one or more of theabove-described environments.

FIG. 46 depicts an exemplary environment featuring a camera mounted on abuilding configured to observe a person.

FIGS. 47-51 each depict intensive and extensive operations that may beperformed in conjunction with one or more high-level logic flows shownin FIG. 15-19 or 38-44.

DETAILED DESCRIPTION

For a more complete understanding of embodiments, reference now is madeto the following descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical items, unless context dictates otherwise.The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented here.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware in one or moremachines, compositions of matter, and articles of manufacture, limitedto patentable subject matter under 35 USC 101. Hence, there are severalpossible vehicles by which the processes and/or devices and/or othertechnologies described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary. Those skilled in the art willrecognize that optical aspects of implementations will typically employoptically-oriented hardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structuressuitable to operation. Electronic circuitry, for example, may manifestone or more paths of electrical current constructed and arranged toimplement various logic functions as described herein. In someimplementations, one or more media are configured to bear adevice-detectable implementation if such media hold or transmit aspecial-purpose device instruction set operable to perform as describedherein. In some variants, for example, this may manifest as an update orother modification of existing software or firmware, or of gate arraysor other programmable hardware, such as by performing a reception of ora transmission of one or more instructions in relation to one or moreoperations described herein. Alternatively or additionally, in somevariants, an implementation may include special-purpose hardware,software, firmware components, and/or general-purpose componentsexecuting or otherwise invoking special-purpose components.Specifications or other implementations may be transmitted by one ormore instances of tangible transmission media as described herein,optionally by packet transmission or otherwise by passing throughdistributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or otherwise invoking circuitry forenabling, triggering, coordinating, requesting, or otherwise causing oneor more occurrences of any functional operations described below. Insome variants, operational or other logical descriptions herein may beexpressed directly as source code and compiled or otherwise invoked asan executable instruction sequence. In some contexts, for example, C++or other code sequences can be compiled directly or otherwiseimplemented in high-level descriptor languages (e.g., alogic-synthesizable language, a hardware description language, ahardware design simulation, and/or other such similar mode(s) ofexpression). Alternatively or additionally, some or all of the logicalexpression may be manifested as a Verilog-type hardware description orother circuitry model before physical implementation in hardware,especially for basic operations or timing-critical applications. Thoseskilled in the art will recognize how to obtain, configure, and optimizesuitable transmission or computational elements, material supplies,actuators, or other common structures in light of these teachings.

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101. Consequently, as usedherein “electro-mechanical system” includes, but is not limited to,electrical circuitry operably coupled with a transducer (e.g., anactuator, a motor, a piezoelectric crystal, a Micro Electro MechanicalSystem (MEMS), etc.), electrical circuitry having at least one discreteelectrical circuit, electrical circuitry having at least one integratedcircuit, electrical circuitry having at least one application specificintegrated circuit, electrical circuitry forming a general purposecomputing device configured by a computer program (e.g., a generalpurpose computer configured by a computer program which at leastpartially carries out processes and/or devices described herein, or amicroprocessor configured by a computer program which at least partiallycarries out processes and/or devices described herein), electricalcircuitry forming a memory device (e.g., forms of memory (e.g., randomaccess, flash, read only, etc.)), electrical circuitry forming acommunications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs (e.g., graphene basedcircuitry). Those skilled in the art will also appreciate that examplesof electro-mechanical systems include but are not limited to a varietyof consumer electronics systems, medical devices, as well as othersystems such as motorized transport systems, factory automation systems,security systems, and/or communication/computing systems. Those skilledin the art will recognize that electro-mechanical as used herein is notnecessarily limited to a system that has both electrical and mechanicalactuation except as context may dictate otherwise.

In a general sense, those skilled in the art will also recognize thatthe various aspects described herein which can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, and/or any combination thereof can be viewed as being composedof various types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof, limited to patentable subject matter under 35 U.S.C. 101.

Those skilled in the art will further recognize that at least a portionof the devices and/or processes described herein can be integrated intoan image processing system. A typical image processing system maygenerally include one or more of a system unit housing, a video displaydevice, memory such as volatile or non-volatile memory, processors suchas microprocessors or digital signal processors, computational entitiessuch as operating systems, drivers, applications programs, one or moreinteraction devices (e.g., a touch pad, a touch screen, an antenna,etc.), control systems including feedback loops and control motors(e.g., feedback for sensing lens position and/or velocity; controlmotors for moving/distorting lenses to give desired focuses). An imageprocessing system may be implemented utilizing suitable commerciallyavailable components, such as those typically found in digital stillsystems and/or digital motion systems.

Those skilled in the art will likewise recognize that at least some ofthe devices and/or processes described herein can be integrated into adata processing system. Those having skill in the art will recognizethat a data processing system generally includes one or more of a systemunit housing, a video display device, memory such as volatile ornon-volatile memory, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices (e.g., a touch pad, a touch screen, an antenna,etc.), and/or control systems including feedback loops and controlmotors (e.g., feedback for sensing position and/or velocity; controlmotors for moving and/or adjusting components and/or quantities). A dataprocessing system may be implemented utilizing suitable commerciallyavailable components, such as those typically found in datacomputing/communication and/or network computing/communication systems.

FIG. 1 depicts a context in which one or more technologies may beimplemented. System 1 comprises a primary unit 110 that may comprise oneor more instances of inputs 121; outputs 122; enlistment modules 133,134; coordinate communication modules 136, 137; data acquisition modules138, 139; interface control modules 141, 142; entity identificationmodules 143, 144; name recognition modules 146, 147; tracking controlmodules 148, 149; flight control modules 151, 152; data delivery modules153, 154; resource reservation modules 156, 157; or selective retentionmodules 158, 159 as described in further detail below. In some contexts,primary unit 110 may be operably coupled to one or more networks 190 viaone or more communication linkages 140. Instances of storage or otherdata-handling media 195 operably coupled to one or more such modulesmay, moreover, reside in primary unit 110 or network 190, as describedbelow. As exemplified herein, a “module” may include special-purposehardware, general-purpose hardware configured with special-purposesoftware, or other circuitry configured to perform one or more functionsrecited below. Also in some contexts such “modules” may be configured toestablish or utilize an association (between two devices, e.g.) inresponse to common interactions (a backup from one device to the other,both logging into a password-access account, or sharing the same printeror router or other peripheral, e.g.). Moreover respective embodiments ofprimary unit 110 may implement substantially any combination thereof, asexemplified in protocols described below.

FIG. 2 depicts another context in which one or more technologies may beimplemented. System 2 comprises a kiosk 250 having several bays 288 eachlarge enough to receive a respective unmanned aerial device (UAD) 201,202 and accessible to one or more users 226. In some variants kiosk 250may also include one or more beacons 217 configured to emit an opticalor other wireless homing signal 296 recognizable to one or more UAD's201, 202. The signal 296 is distinctive enough to facilitate UAD's 201,202 finding beacon 217 several meters or more away from kiosk 250.Moreover each of the bays 288 has protruding or recessed electricalcontacts 298 therein to permit each UAD 201, 202 to recharge after it isplaced or lands within the bay.

FIG. 3 depicts another system 3 in which one or more technologies may beimplemented, one in which one or more instances of a name 351, model352, or other identifier 355 refer to and identify interface device 310.In a context in which interface device 310 comprises a minivan or otherpassenger vehicle, for example, such identifier(s) 355 may comprise aplate number 353 of the vehicle. As explained below, interface device310 may further include one or more instances (implemented inspecial-purpose circuitry or software executable by one or moreprocessors 365, e.g.) of modes 361, 362, 363; requests 373; invitations374; reservations 376; confirmations 381, 382; touchscreens or otherlocal interfaces 390 (comprising one or more inputs 391 or outputs 392physically accessible to or observable by a user at interface device310, e.g.); acceptances 393, 394; memories 395; or instructions 397.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for conducting a context-specific structured dialog or otheruser interaction without undue experimentation or for configuring otherdecisions and devices as described herein. See, e.g., U.S. Pat. No.8,024,329 (“Using inverted indexes for contextual personalizedinformation retrieval”); U.S. Pat. No. 7,970,735 (“Cross varyingdimension support for analysis services engine”); U.S. Pat. No.7,920,678 (“Personal virtual assistant”); U.S. Pat. No. 7,870,117(“Constructing a search query to execute a contextual personalizedsearch of a knowledge base”); U.S. Pat. No. 7,761,480 (“Informationaccess using ontologies”); U.S. Pat. No. 7,743,051 (“Methods, systems,and user interface for e-mail search and retrieval”); U.S. Pat. No.7,593,982 (“Method, system, and computer program product for saving asearch result within a global computer network”); U.S. Pat. No.7,363,246 (“System and method for enhancing buyer and seller interactionduring a group-buying sale”); U.S. Pat. No. 7,177,948 (“Method andapparatus for enhancing online searching sale”); U.S. Pat. No. 6,798,867(“System and method for the creation and automatic deployment ofpersonalized, dynamic and interactive voice services, with real-timedatabase queries”); U.S. Pub. No. 2011/0081053 (“Methods and systems forocclusion tolerant face recognition”); U.S. Pub. No. 2008/0159622(“Target object recognition in images and video”).

Referring again to FIG. 1, network 190 may serve as a context forintroducing one or more processes, systems or other articles describedbelow. In some instances network 190 may include one or more searchengines, satellites, servers, processors, routers, or other devices. Insome contexts, one or more interface devices owned or operated by user226 may interact through network 190 (e.g. with one or more otherinterface devices or networks as described herein). One or more suchassociated interface devices 310 may be mobile devices, in somecontexts, or may function in cooperation (as a network subsystem, e.g.)even when remote from one another. Alternatively or additionally, one ormore other interface devices owned or operated by user 226 may likewiseinteract locally or remotely with or through one another or otherinterface devices (through network 190, e.g.).

In some contexts, such interface devices (of FIG. 2, e.g.) may includeor otherwise communicate with one or more instances of primary unit 110and may include one or more instances of data outputs or otherimplementations of machines, articles of manufacture, or compositions ofmatter that include circuitry or other logic as described below. In somecontexts, such implementations may be held or transmitted by conduits,storage devices, memories, other holding devices, or other circuitry forhandling data or software (in a satellite, server, or router, e.g.) asdescribed herein. In various embodiments, one or more instances ofimplementation components or implementation output data may each beexpressed within any aspect or combination of software, firmware, orhardware as signals, data, designs, logic, instructions, or other suchspecial-purpose expression or implementation. Interface devices (such asthat of FIG. 2, e.g.) may likewise include one or more instances oflenses, transmitters, receivers, integrated circuits, antennas, outputdevices, reflectors, or input devices for handling data or communicatingwith local users or via linkage 140, for example.

Those skilled in the art will recognize that some list items may alsofunction as other list items. In the above-listed types of media, forexample, some instances of interface devices may include conduits or mayalso function as storage devices that are also holding devices. One ormore transmitters may likewise include input devices or bidirectionaluser interfaces, in many implementations of interface devices 310. Eachsuch listed term should not be narrowed by any implication from otherterms in the same list but should instead be understood in its broadestreasonable interpretation as understood by those skilled in the art.

“Apparent,” “automatic,” “selective,” “conditional,” “indicative,”“normal,” “represented,” “related,” “partly,” “responsive,” “distilled,”“local,” “in a vicinity,” “remote,” “wireless,” “periodic,” “free,”“aerial,” “associated,” “primary,” “met,” “passive,” “implemented,”“executable,” “particular,” “specific,” “human,” “performed,” “impeded,”“engaged,” “earlier,” “later,” “detectable,” “mobile,” “of,” “prior,”“activated,” “future,” “light,” “contemporaneous,” “portable,” “toward,”or other such descriptors herein are used in their normal yes-or-nosense, not as terms of degree, unless context dictates otherwise. Inlight of the present disclosure those skilled in the art will understandfrom context what is meant by “vicinity,” by being “in” or “at” adetection region, by “remote,” and by other such positional descriptorsused herein. “For” is not used to articulate a mere intended purpose inphrases like “circuitry for” or “instruction for,” moreover, but is usednormally, in descriptively identifying special purpose circuitry orcode.

Some descriptions herein refer to a “distillation” of data. Suchdistillations can include an average, estimate, range, or othercomputation at least partly distilling a set of data. They can likewiseinclude an indexing, sorting, summarization, distributed sampling, orother process having a purpose or effect of showing some aspect of thedata more concisely or effectively than a conventional display orarchiving of the entire data. Selecting a last portion of a data set canconstitute a distillation, for example, in a context in which the data'sutility apparently increases (medians or other cumulative computations,e.g.). Removing duplicative data or indexing available data are usefulways of “distilling” data so that it becomes manageable even whileretaining some of its meaning. Those skilled in the art will recognizemany useful modes of distilling data in light of the state of the artand of teachings herein.

In some embodiments, “signaling” something can include identifying,contacting, requesting, selecting, or indicating the thing. In somecases a signaled thing is susceptible to fewer than all of theseaspects, of course, such as a task definition that cannot be“contacted.”

In some embodiments, “status indicative” data can reflect a trend orother time-dependent phenomenon (indicating some aspect of an entity'scondition, e.g.). Alternatively or additionally, a status indicativedata set can include portions that have no bearing upon such status.Although some types of distillations can require authority orsubstantial expertise (e.g. making a final decision upon a riskyprocedure or other course of action), many other types of distillationscan readily be implemented without undue experimentation in light ofteachings herein.

In some embodiments, one or more applicable “criteria” can includemaxima or other comparison values applied to durations, counts, lengths,widths, frequencies, signal magnitudes or phases, digital values, orother aspects of data characterization. In some contexts, such criteriacan be applied by determining when or how often a recognizable patterncan be found: a text string, a quantity, a sound, an arrhythmia, avisible dilation, a failure to respond, a non-change, an allergicresponse, a symptom relating to an apparent condition of the user, orthe like.

In some embodiments, “causing” events can include triggering, producingor otherwise directly or indirectly bringing the events to pass. Thiscan include causing the events remotely, concurrently, partially, orotherwise as a “cause in fact,” whether or not a more immediate causealso exists.

Some descriptions herein refer to an “indication whether” an event hasoccurred. An indication is “positive” if it indicates that the event hasoccurred, irrespective of its numerical sign or lack thereof, limited topatentable subject matter under 35 U.S.C. 101. Whether positive ornegative, such indications may be weak (i.e. slightly probative),definitive, or many levels in between. In some cases the “indication”may include a portion that is indeterminate, such as an irrelevantportion of a useful photograph.

FIG. 4 depicts another system 4 in which one or more technologies may beimplemented. Event/condition detection unit 400 comprisesspecial-purpose circuitry implemented as one or moreapplication-specific integrated circuits (ASICs) 409 or other suchdata-handling media 410. Event/condition detection unit 400 may, in somevariants, include one or more instances of data 411, 412, 413;hard-wired or other special-purpose protocols 417, 418; triggers 421,422, 423; decisions 434, 435; microphones 441 or other receivers 442;identifiers 444; proximity sensors 449; wireless signal processingmodules 450 (operable to handle one or more signals 451, 452, 453, 434transmitted or received via antenna 455, e.g.); thresholds 458, 459;configurations 471, 472; commands 481, 482, 483, 484, 485; or tasks 491,492, 493, 494, 495, 496, 497, 498, 499 (implemented in special-purposecircuitry or software executable by one or more processors 365, e.g.).In some variants, such commands 481-485 or tasks 491-499 may be received(from user 226, e.g.) via a microphone 441 and a speech recognitionmodule 446, 447 or other such configurations of inputs 391. (In someembodiments, a “module” as described herein may include one or more ofspecial-purpose circuitry or special-purpose device-executable code:code by which a processor 365 that is executing the code, for example,becomes a special-purpose machine.)

FIG. 5 depicts another system 5 in which one or more technologies may beimplemented. An unmanned aerial device (UAD) 501 may travel among asender 510 (of cargo to be delivered, e.g.), a station 520, and adestination 530 (of the cargo, e.g.) along travel paths 581, 582, 583through the air 585 as shown. One or more media 195, 410 aboard UAD 501may contain one or more identifiers 541 of cargo, identifiers 542 ofdestination 530, or identifiers 543 of the UAD 501 tasked with delivery.Such media may likewise contain other indicia of various planned orcompleted delivery tasks 491-499, such as a photograph 553 of an item ofcargo (envelope 551, e.g.) having been delivered to a delivery site 552(at destination 530, e.g.); a photograph 554 of a part of a recipient555 or of an item of cargo (syringe 556, e.g.) being delivered to adestination (recipient 555, e.g.); addresses (of sender 510, station520, or destination 530, e.g.); audio clips 563 (of recipient 555refusing or accepting delivery, e.g.); or biometrics 564 (of sender 510or recipient 555, e.g.). In some implementations, moreover, UAD 501 mayimplement or interact with one or more instances of interfaces 390(having one or more buttons 561 thereon as inputs 391, e.g.) asdescribed below.

With reference now to FIG. 15, shown is a high-level logic flow 15 of anoperational process. Intensive operation 53 describes obtaining firstdata indicating that a first unmanned aerial device delivered a firstitem to a first entity (e.g. data acquisition module 138 receiving oneor more addresses 562 or photographs 553 as data 411 indicating that oneor more UAD's 501 delivered an envelope 551, signature document, orother article to a placement site 552 or other destination 530). Thiscan occur, for example, in a context in which UAD 501 implements orinteracts with primary unit 110, UAD 201, and event/condition detectionunit 400 as described above. Alternatively or additionally, data 412 mayinclude a biometric 564 (fingerprint, e.g.) or other manifestation of arecipient 555 receiving a medication (in a syringe 556 or capsule, e.g.)or other delivered material as described herein. Either such “first”data 411, 412 may likewise include one or more of an identifier 541 ofthe “first” item (envelope 551 or syringe 556, e.g.), an identifier 542of the “first” entity (site 552 or recipient 555, e.g.), an identifier543 (serial number or alias, e.g.) of the “first” UAD 201, 501 or othersuch indications signifying a successful delivery.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for dispatching a vehicle for making deliveries without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,140,592 (“Deliveryoperations information system with route adjustment feature and methodsof use”); U.S. Pat. No. 8,041,649 (“Methods and systems forpostcode-to-postcode delivery interval and routing calculation”); U.S.Pat. No. 7,947,916 (“Mail sorter system and method for moving trays ofmail to dispatch in delivery order”); U.S. Pat. No. 7,868,264 (“Systemand process for reducing number of stops on delivery route byidentification of standard class mail”); U.S. Pat. No. 7,739,202(“Computer system for routing package deliveries”); U.S. Pat. No.7,647,875 (“Seed hopper and routing structure for varying materialdelivery to row units”); U.S. Pat. No. 6,801,139 (“Method and system fordelivering a time-efficient mobile vehicle route that encompassesmultiple limited-duration events”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for data acquisition (relating to a delivery, e.g.) withoutundue experimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,111,819 (“Message serverand method for notification of a user about the delivery of anelectronic message”); U.S. Pat. No. 8,074,642 (“Visual indicator for anaerosol medication delivery apparatus and system”); U.S. Pat. No.7,984,100 (“Email system automatically notifying sender status androuting information during delivery”); U.S. Pat. No. 7,713,229 (“Drugdelivery pen with event notification means”); U.S. Pat. No. 7,559,456(“Mail delivery indicator system”); U.S. Pat. No. 7,222,081 (“System andmethod for continuous delivery schedule including automated customernotification”); U.S. Pat. No. 6,902,109 (“Parcel delivery notice”); U.S.Pat. No. 6,859,722 (“Notification systems and methods with notificationsbased upon prior package delivery”); U.S. Pat. No. 6,535,585 (“Systemand method for notification upon successful message delivery”); U.S.Pat. No. 6,356,196 (“Verified receipt, notification, and theftdeterrence of courier-delivered parcels”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for detecting and responding automatically to position data,optical data, auditory data, or other indications of a delivery withoutundue experimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,131,652 (“Residentialdelivery indicator”); U.S. Pat. No. 7,559,456 (“Mail delivery indicatorsystem”); U.S. Pat. No. 7,483,721 (“Communication device providingdiverse audio signals to indicate receipt of a call or message”); U.S.Pat. No. 7,346,662 (“Methods, systems, and products for indicatingreceipt of electronic mail”); U.S. Pat. No. 7,013,350 (“System settingflags based on address types in destination address field of a messageto indicate different transports to deliver the message”); U.S. Pat. No.7,006,013 (“System and method for visually indicating receipt of a radiocommunication directed to a uniquely identified vehicle”).

In some embodiments described herein, a response (generating a decision,e.g.) to a stimulus is “conditional” if the stimulus can take on eithera first possible value or a second possible value (or perhaps others)and in which the content (yes or no, e.g.) or occurrence of the responsedepends upon which of the possible stimuli are manifested. Likewise aresponse is “automatic” if it can occur (for at least one possiblestimulus set, e.g.) without any human interaction.

Referring again to FIG. 15, extensive operation 84 describestransmitting via a free space medium the first data to a provider of thefirst item as an automatic and conditional response to the first dataindicating that the first unmanned aerial device delivered the firstitem to the first entity, the first data indicating at least one of thefirst item or the first entity or the first unmanned aerial device (e.g.data delivery module 153 transmitting a wireless signal 454 (radiofrequency, e.g.) containing data 411, 412 indicating a delivery of thefirst item to the sender 510 of the first item). This can occur, forexample, in a context in which data delivery module 153 receives suchfirst data from data acquisition module 138; in which the first itemcomprises an envelope 551, syringe 556, material, or other such articlesphysically delivered by one or more UAD's 201, 501 to destination 530;in which such a UAD includes a data delivery module 153 configured totransmit such first data via a wireless signal path 581 (through air 585or water vapor, e.g.); and in which sender 510 would otherwise beunwilling to entrust the item to be transferred via UAD 501.Alternatively or additionally, such a data delivery module 153 may beconfigured to transmit such first data indirectly (via a wireless signalpath 583 through air 585 and through a station 520 that relays signal454 to sender 510, e.g.). Alternatively or additionally, station 520 mayinclude (an instance of) a data delivery module 153 configured toperform operation 84 by transmitting some or all such data 411, 412wirelessly via path 582 as an automatic and conditional response to asuitable trigger 421. In respective embodiments, for example, a primaryunit 110 may be configured to perform flow 15 such that trigger 421comprises any of (1) UAD 501 delivering the first item to destination530; (2) UAD 501 arriving at station 520 after having delivered thefirst item to destination 530; or (3) data delivery module 153 receivingan indication that UAD 201 delivered the first item to destination 530.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for deciding whether or not to route data through a free spacemedium without undue experimentation or for configuring other decisionsand devices as described herein. See, e.g., U.S. Pat. No. 8,175,025(“Wireless communication apparatus for selecting suitable transfer routeon wireless network”); U.S. Pat. No. 8,099,060 (“Wireless/wired mobilecommunication device with option to automatically block wirelesscommunication when connected for wired communication”); U.S. Pat. No.8,090,132 (“Wireless communication headset with wired and wirelessmodes”); U.S. Pat. No. 8,081,967 (“Method to manage medium access for amixed wireless network”); U.S. Pat. No. 8,040,864 (“Map indicatingquality of service for delivery of video data to wireless device”); U.S.Pat. No. 7,899,027 (“Automatic route configuration in hierarchicalwireless mesh networks”); U.S. Pat. No. 7,869,444 (“Mixed wireless andcabled data acquisition network”); U.S. Pat. No. 7,865,186 (“Method foroperating wired and wireless phone services interconnectively”); U.S.Pat. No. 7,315,548 (“Method and apparatus for determining a routebetween a source node and a destination node in a wireless multihoppingcommunication network”); U.S. Pat. No. 6,578,085 (“System and method forroute optimization in a wireless internet protocol network”); U.S. Pat.No. 6,058,312 (“Automatic selecting apparatus for an optimum wirelesscommunication route”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for mobile data delivery (deciding when to transmit data fromor via a mobile device, e.g.) without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,200,223 (“Base station and data transfer method fortransferring data when a mobile station performs a handover”); U.S. Pat.No. 7,865,212 (“Methods and apparatus for use in transferring user databetween two different mobile communication devices using a removablememory card”); U.S. Pat. No. 7,359,346 (“Apparatus for controlling datatransmission/reception between main system and remote system of BTS inmobile communication system”); U.S. Pat. No. 7,240,075 (“Interactivegenerating query related to telestrator data designating at least aportion of the still image frame and data identifying a user isgenerated from the user designating a selected region on the displayscreen, transmitting the query to the remote information system”); U.S.Pat. No. 7,107,064 (“Mobile communication device and method fordetermining whether to transmit position data”); U.S. Pat. No. 6,742,037(“Method and apparatus for dynamic information transfer from a mobiletarget to a fixed target that tracks their relative movement andsynchronizes data between them”); U.S. Pat. No. 6,694,177 (“Control ofdata transmission between a remote monitoring unit and a central unit”);U.S. Pat. No. 6,604,038 (“Apparatus, method, and computer programproduct for establishing a remote data link with a vehicle with minimaldata transmission delay”); U.S. Pat. No. 6,591,101 (“Method ofsubscriber data control in a mobile communication network wheresubscriber data is transferred from a home mobile switching center to adestination mobile switching center”).

FIG. 6 depicts another system 6 in which one or more technologies may beimplemented, one involving a passenger vehicle (car 602, e.g.) withwheels 683, pontoons, or other such support structures configured tofacilitate transportation. As shown, car 602 is configured to bear atleast one person (user 626, e.g.) and to include a user interface 660(navigation system, e.g.). In a context in which such a passengervehicle approaches an entrance 641 of a parking lot, UAD 601 may beconfigured (in association with the vehicle or with a zone comprisingthe parking lot, e.g.) to transmit to the vehicle information ofinterest. Such information can include coordinates 605, 606 (indicatingan open parking space 648 or other location of interest, e.g.) or otherpositional information (indicating a recommended path 643 or waypoint642 thereof, e.g.) transmitted via a wireless communication linkage 694.

With reference now to FIG. 16, shown is a high-level logic flow 16 of anoperational process. Intensive operation 51 describes obtaining firstposition data from a first entity, by a second entity, the first entitybeing a first unmanned aerial device (e.g. a coordinate communicationmodule 136 resident in car 602 receiving two or more coordinates 605from UAD 601 indicating the position of UAD 601). This can occur, forexample, in a context in which UAD 601 implements one or more UAD's 201,501 as described above; in which an instance of primary unit 110 isresident in one or both of the “first” and “second” entities; in whichthe “second” entity (car 602 or user 626, e.g.) has arrived at anentrance 641 of a crowded parking lot; in which UAD 601 has found andoccupied a vacant parking space 648; and in which UAD 601 transmits itslocation (to a user interface 660 of the “second” entity, e.g.) via awireless linkage 694 to assist a device or user (in finding andoccupying the parking space 648, e.g.). In some contexts, the first UAD601 may include an interface control module 141 configured to transmitturn-by-turn instructions, coordinates 605, or other such guidance, forexample. See FIG. 17. Such guidance can, for example, lead a “second”device (UAD 202 or car 602, e.g.) or user 226, 626 thereof to a pickupor delivery site 552, an article or other material there, a person in acrowd, or other such resources and destinations having locations knownto primary unit 110.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for coordinate communication (acquiring, transmitting,receiving, or using altitude or other positional coordinates, e.g.)without undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,107,608 (“Systemand method for providing routing, mapping, and relative positioninformation to users of a communication network”); U.S. Pat. No.8,041,453 (“Method and apparatus for defining and utilizing productlocation in a vending machine”); U.S. Pat. No. 8,009,058 (“Trackinglocation and usage of a mechanical sub assembly (MSA) within anautomated storage library utilizing a unique identifier associated withlocation coordinates of the MSA”); U.S. Pat. No. 7,819,315 (“Apparatusand method for providing product location information to customers in astore”); U.S. Pat. No. 7,705,714 (“Wheel position detecting device thatperforms dedicated local communication for each wheel and tire airpressure detecting device including the same”); U.S. Pat. No. 7,555,386(“System and method for sharing position information using mobilecommunication system”); U.S. Pat. No. 6,609,317 (“Signs for display ofstore item location systems”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for locating particular individuals or other mobile targetswithout undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,200,247(“Confirming a venue of user location”); U.S. Pat. No. 8,106,746(“Method, apparatus, and system for selecting and locating objectshaving radio frequency identification (RFID) tags”); U.S. Pat. No.8,064,647 (“System for iris detection tracking and recognition at adistance”); U.S. Pat. No. 8,032,153 (“Multiple location estimators forwireless location”); U.S. Pat. No. 7,925,093 (“Image recognitionapparatus”); U.S. Pat. No. 7,893,848 (“Apparatus and method forlocating, identifying and tracking vehicles in a parking area”); U.S.Pat. No. 7,876,215 (“System and method for locating and notifying amobile user of people having attributes or interests matching a statedpreference”); U.S. Pat. No. 7,656,292 (“Flexible anti-theft pack fortracking and location”); U.S. Pat. No. 7,647,171 (“Learning, storing,analyzing, and reasoning about the loss of location-identifyingsignals”); U.S. Pat. No. 7,092,566 (“Object recognition system andprocess for identifying people and objects in an image of a scene”);U.S. Pat. No. 6,513,015 (“System and method for customer recognitionusing wireless identification and visual data transmission”); U.S. Pat.No. 6,219,639 (“Method and apparatus for recognizing identity ofindividuals employing synchronized biometrics”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for locating specific resources without undue experimentationor for configuring other decisions and devices as described herein. See,e.g., U.S. Pat. No. 8,194,975 (“Use of an intrinsic image in facerecognition”); U.S. Pat. No. 7,659,835 (“Method and apparatus forrecognizing parking slot by using bird's eye view and parking assistsystem using the same”); U.S. Pat. No. 7,480,394 (“Method andarrangement for recognizing objects in mail item images, their positionand reading their postal information”); U.S. Pat. No. 6,592,033 (“Itemrecognition method and apparatus”); U.S. Pat. No. 6,373,982 (“Processand equipment for recognition of a pattern on an item presented”); U.S.Pat. No. 6,313,745 (“System and method for fitting room merchandise itemrecognition using wireless tag”); U.S. Pat. No. 6,121,916 (“Method andapparatus for recognizing stationary objects with a moving side-lookingradar”).

Referring again to FIG. 16, extensive operation 83 describes signaling adecision whether or not to allocate a first resource to the secondentity after the first position data passes from the first unmannedaerial device to the second entity, the first resource being associatedwith the first position data (e.g. resource reservation module 156confirming a reservation 376 of parking space 648 after coordinates 605thereof arrive at user interface 660). This can occur, for example, in acontext in which parking space 648 is the “first” resource; in which the“second” entity is identified as the driver (by name 351, e.g.) or asthe car (by model 352 or license plate number 353, e.g.); in which UAD601 and user interface 660 each contain an instance of primary unit 110;in which UAD 601 receives and announces one or more such identifiers(via a speaker, projector, or other output 122 of UAD 601, e.g.) topassersby; in which user 626 enters the decision by indicating whetheror not to associate the “first” resource with an identifier 355 of thesecond entity via input 121 of user interface 660; and in which user 626would otherwise be unable to reserve the resource before happeningacross it. In other applications of flow 16, such “first” resources mayinclude a cashier or other living entity; a public table or other space;a power or network connection; an item for sale or other object; orother such resources that a device can deem available for allocationunder conditions as described herein. Moreover such “second” entitiesmay include UAD's or other devices or people as described herein(identified by entity identification module 143, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for entity identification (associating a specific identifierwith a device, user, group, or other entity, e.g.) without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,176,156 (“Serveridentification assignment in a distributed switched storageenvironment”); U.S. Pat. No. 8,136,025 (“Assigning documentidentification tags”); U.S. Pat. No. 7,970,426 (“Method of assigningprovisional identification to a subscriber unit and group”); U.S. Pat.No. 7,877,515 (“Identity assignment for software components”); U.S. Pat.No. 7,495,576 (“Modular electronic sign and method of assigning a uniqueidentifier to common modules of said sign”); U.S. Pat. No. 7,383,174(“Method for generating and assigning identifying tags to sound files”);U.S. Pat. No. 6,721,761 (“System for assigning digital identifiers totelephone numbers and IP numbers”); U.S. Pat. No. 6,430,182 (“Fabricsystem and method for assigning identifier for fabric apparatustherefor”); U.S. Pat. No. 6,283,227 (“Downhole activation system thatassigns and retrieves identifiers”); U.S. Pat. No. 6,114,970 (“Method ofassigning a device identification”); U.S. Pat. No. 6,091,738(“Transmission-equipment and method for assigning transmission-equipmentidentification number in transmission system”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for resource reservation (associating an entity identifierwith a living or other resource, e.g.) without undue experimentation orfor configuring other decisions and devices as described herein. See,e.g., U.S. Pat. No. 8,166,484 (“System for confirming and cancellingtentative resource reservation within the valid time indicates periodduring which the tentative reservation request is valid”); U.S. Pat. No.8,160,906 (“System and method for improved rental vehicle reservationmanagement”); U.S. Pat. No. 8,150,403 (“Reservation of mobile stationcommunication resources”); U.S. Pat. No. 8,117,051 (“Method fordetermining the number of available transport seats in a computerizedreservation system”); U.S. Pat. No. 8,065,287 (“Method and system forsearching availability of an entity for purchase or reservation”); U.S.Pat. No. 7,956,769 (“Method and system for reservation-based parking”);U.S. Pat. No. 7,818,190 (“Camping reservation system, method andprogram”); U.S. Pat. No. 7,783,530 (“Parking reservation systems andrelated methods”); U.S. Pat. No. 7,783,506 (“System and method formanaging reservation requests for one or more inventory items”); U.S.Pat. No. 7,693,779 (“Method and system for requesting a reservation fora set of equity instruments to be offered”); U.S. Pat. No. 7,634,426(“Golf reservation system”); U.S. Pat. No. 7,548,866 (“Individual seatselection ticketing and reservation system”).

FIG. 7 depicts another system 7 in which one or more technologies may beimplemented, depicting a view from above of several people 725, 726, 727near a zone boundary 789 dividing two zones 781, 782 (areas of land,e.g.). Person 726 is shown carrying an unmanned aerial device 701containing itineraries 761, 762 (in a memory 395 or other medium 195thereof, e.g.) in one or more contexts further described below. In onecontext, person 726 is walking, and UAD 701 is traveling, toward aperson 725 or device 775 that is currently a distance 788 away. Inanother, the destination 530 is defined as a vicinity 785 (a detectionrange of a proximity sensor 449, e.g.) of such a device 775. In anothercontext, UAD 701 is guiding person 726 generally along a static ordynamic path 743 comprising a waypoint 742. In yet another context, asubject (person 727, e.g.) has one or more attributes (clothing 728 orvoice or face or other biometric 564, e.g.) susceptible of automaticrecognition by one or more stationary event/condition detection units400 or other recognition modules (aboard a UAD 701 or other portabledevice 775, e.g.). See FIG. 14.

With reference now to FIG. 17, shown is a high-level logic flow 17 of anoperational process. Intensive operation 52 describes causing a firstunmanned aerial device to guide a first individual to a firstdestination (e.g. interface control module 141 causing a display,speaker, or other output 392 of unmanned aerial device 701 to providenavigational instruction 397 effective for guiding person 726 accordingto a first itinerary 761). This can occur, for example, in a context inwhich the first destination is a vicinity 785 of a person 725 or of aportable device 775; in which the first destination is also anon-stationary component of the first itinerary 761 (indicating such aperson 725, device 775, or other destination, e.g.); in which person 726is the “first” individual, who may be traveling through a zone 782 inwhich conventional GPS navigation devices cannot be used; and in whichperson 726 would otherwise have to find the “first” destination withoutany device assistance. On a cruise ship or tightly managed facility inwhich an owner (of zone 782, e.g.) does not provide a public wirelessconnectivity (cell tower access, e.g.) or in which individuals are notpermitted to bring their own wireless devices onsite, for example, theowner may lend such UAD's 701 to visitors for authorized uses (finding astationary or other destination 530 within or across a controlled zone782, e.g.). Alternatively, in some variants, a flight control module 151may perform operation 52 by flying ahead of the first individual (user626, e.g.) slow enough to be followed. This can occur, for example, in acontext in which itinerary 761 defines the first destination (parkingspace 648, e.g.) and in which flight control module 151 is configured torespond to a microphone, accelerometer, camera, or other input 391 of a“first” UAD signaling such flying guidance. For example, flight controlmodule 151 may be configured to cause the first UAD to maintain asuitable lead distance (on the order of 1-3 meters, e.g.) of the firstindividual in some contexts, landing or otherwise slowing down asnecessary if the individual follows slowly, moving laterally or backwardif the individual moves orthogonally to or opposite to the first UAD'scurrent or next direction of travel, giving up (and returning to a kiosk250 or other “home” station, e.g.) if the individual stops following fora period of time exceeding a threshold (on the order of 1 or 60 seconds,e.g.).

Alternatively or additionally, an instance of flight control module 151aboard UAD 701 may be configured (by including a microphone 441operatively coupled to a speech recognition module 446, e.g.) torecognize and conditionally follow one or more commands given by thefirst person (“stay with me” or “fly away” e.g.). In some variants, forexample, such a command 482 of “stay with me” can conditionally cause anoverride or modification of a default configuration of flight controlmodule 151 so that flight control module 152 is temporarily disabled orso that itinerary 762 is suspended until after speech recognition module446 detects and signals the “fly away” command 483 (to one or moreflight control modules 151, 152, e.g.). This can occur, for example, ina context in which the latter event defines an alternative trigger 422causing the first UAD to fly to a “home” station (or a “second”destination, e.g.) defined by itinerary 762 under the control of flightcontrol module 152.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for interface control (remotely or locally controlling how aninterface handles user input or output, e.g.) without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,201,143 (“Dynamic mating ofa modified user interface with pre-modified user interface codelibrary”); U.S. Pat. No. 8,198,568 (“Input sensitive user interface”);U.S. Pat. No. 8,185,483 (“System for design and use of decisionmodels”); U.S. Pat. No. 8,184,070 (“Method and system for selecting auser interface for a wearable computing device”); U.S. Pat. No.8,181,119 (“User interface with inline customization”); U.S. Pat. No.8,171,460 (“System and method for user interface automation”); U.S. Pat.No. 8,171,394 (“Methods and systems for providing a customized userinterface for viewing and editing meta-data”); U.S. Pat. No. 8,165,567(“Method and system for customizing user interface by editing multimediacontent”); U.S. Pat. No. 8,151,201 (“User interface manager and methodfor reacting to a change in system status”); U.S. Pat. No. 8,127,233(“Remote user interface updates using difference and motion encoding”);U.S. Pat. No. 8,122,365 (“System and method for dynamic creation andcustomization of a user interface in a web service environment”); U.S.Pat. No. 7,908,221 (“System providing methods for dynamic customizationand personalization of user interface”).

Referring again to FIG. 17, extensive operation 85 describes causing thefirst unmanned aerial device to fly to a second destination as anautomatic and conditional response to an indication of the firstindividual arriving at the first destination (e.g. flight control module152 causing a “first” UAD 701 to fly to a kiosk 250 or other station 520as an implementation of an itinerary 762 triggered by the first UADarriving at the first destination). This can occur, for example, in acontext in which the first UAD implements one or more primary units 110or interface devices 310; in which the “second” destination comprisesthe kiosk 250 or other station 520; in which a proximity sensor 449 orother such input 121 (operatively coupled to a flight control module 152of device 775, e.g.) detects that UAD 701 is in a vicinity 785 of device775 (as the indication of the first individual arriving at the firstdestination, e.g.); and in which person 726 would otherwise have toinstruct UAD 701 what to do after arriving. In some variants, forexample, such an input 121 may include a wireless signal processingmodule 450 configured to transmit a first wireless signal 451 andreceive a second wireless signal 452 (echo, e.g.) responsive thereto,the wireless signals 451, 452 jointly manifesting a delay indicative ofa distance 788 between the devices so that a signal 453 derivedtherefrom indicates the first UAD arriving “at” the first destination asthe derived signal 453 crossing a threshold 458, the flight controlmodule 152 being operatively coupled to wireless signal processingmodule 450 and responsive to such crossing. Alternatively oradditionally, network 190 may include an event/condition detection unit400 implemented in UAD 701. In some variants, moreover, one or moreadditional flight control modules 152 may be configured to perform oneor more variants of operation 85 (causing the 1st UAD to fly to a 3nddestination as an automatic and conditional response to an indication ofthe first individual arriving at the 2nd destination or to some otherindication of the first UAD arriving at the 2nd destination, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for flight control (using one or more remote or on-boardcontrollers to cause an aerial device to implement a user-specified orautonomously selected route or itinerary, e.g.) without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,186,589 (“UAV decision andcontrol system”); U.S. Pat. No. 8,100,366 (“Automatic kite flightcontrol system”); U.S. Pat. No. 8,074,941 (“Aircraft flight control”);U.S. Pat. No. 7,962,252 (“Self-contained avionics sensing and flightcontrol system for small unmanned aerial vehicle”); U.S. Pat. No.7,502,684 (“Method and system for the automatic piloting of an aircrafton the approach to an airdrop position”); U.S. Pat. No. 7,431,243(“Guidance and control for an autonomous soaring UAV”); U.S. Pat. No.7,130,741 (“Navigating a UAV with a remote control device”); U.S. Pat.No. 6,926,233 (“Automatic formation flight control system (AFFCS)—asystem for automatic formation flight control of vehicles not limited toaircraft, helicopters, or space platforms”); U.S. Pat. No. 6,856,894(“Navigating a UAV under remote control and manual control with threedimensional flight depiction”); U.S. Pat. No. 6,847,856 (“Method fordetermining juxtaposition of physical components with use of RFIDtags”); U.S. Pat. No. 6,497,600 (“Automatic pilot system for modelaircraft”).

Another system 8 in which one or more technologies may be implemented isshown in FIG. 8, depicting a view of several unmanned aerial devices(UAD's) 801, 802, 803 configured to communicate with a control unit 860on a network 890. Task definition module 870 (residing in control unit860, e.g.) may include one or more aliases 871 in a role list 875(identifying one or more unmet needs of a task 491-499, e.g.) and one ormore aliases (“Hulk,” e.g.) in a participant list 885 or other met needslist 880 of the task or job. UAD 801 comprises a name recognition module810 configured to recognized a primary identifier 811 of UAD 801. UAD802 comprises a name recognition module 820 configured to recognized aprimary identifier 821 of UAD 802 as well as one or more aliases 822,823 of UAD 802. (In some embodiments, one or more aliases or otheridentifiers “of” a device may also refer to a specific circuit orvirtual entity at least partly aboard the device.)

With reference now to FIG. 18, shown is a high-level logic flow 18 of anoperational process. Intensive operation 54 describes indicating a firstunmanned aerial device participating in a first task (e.g. enlistmentmodule 133 generating a confirmation 381 that UAD 801 will participatein a delivery task 491 being coordinated by control unit 860). This canoccur, for example, in a context in which one or more networks 190, 890comprise interface device 310; in which control unit 860 and UAD's 801,802, 803 may each contain (a respective instance of) primary unit 110,each optionally including event/condition detection unit 400; in which(an instance of) enlistment module 133 resides in control unit 840 andtransmits an invitation 374 to UAD 801 to participate in one or moretasks 491-499; and in which UAD 801 transmits a timely acceptance 393 ofthe invitation 374. Alternatively or additionally, one or moreenlistment modules 134 (resident in UAD 801, e.g.) may be configured toidentify tasks 491, 492 suitable for UAD 801 to participate in and maytransmit one or more requests 373 for such participation (to controlunit 860, e.g.). This can occur, for example, in which enlistment module133 is configured to perform an instance of operation 54 by transmittingan acceptance 394 of request 373. In some contexts, such requests 373and invitations 374 (in an instance of network 190 that includes severalUAD's 801, 802, 803 as described above, e.g.) may include a temporalthreshold 459 expressing a deadline at or before which the request orinvitation recipient must respond (as an expiration time of the requestor invitation after which no acceptance of such request 373 orinvitation 374 would be valid, e.g.). Alternatively or additionally, inthe absence of such expression, one or more enlistment modules 133, 134may be configured to apply a default deadline (within 1-2 orders ofmagnitude of a millisecond or a second after such transmission, e.g.),after which such recruitment subtask may be deemed unsuccessful.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for device enlistment (enabling or otherwise causing one ormore available devices to participate in one or more suitable tasks,e.g.) without undue experimentation or for configuring other decisionsand devices as described herein. See, e.g., U.S. Pat. No. 8,151,272(“Optimized usage of collector resources for performance data collectionthrough even task assignment”); U.S. Pat. No. 8,128,484 (“Game systemgenerating second game according to game result of a device and allowingother devices to participate in second game thus generated”); U.S. Pat.No. 8,051,764 (“Fluid control system having selective recruitableactuators”); U.S. Pat. No. 7,948,447 (“Mobile display”); U.S. Pat. No.7,864,702 (“Control and recruitment of client peripherals fromserver-side software”); U.S. Pat. No. 7,406,515 (“System and method forautomated and customizable agent availability and task assignmentmanagement”); U.S. Pat. No. 7,308,472 (“System allowing data inputdevice to request management server to assign a data input job toitself”); U.S. Pat. No. 6,975,820 (“Device control using job ticketscoring”); U.S. Pat. No. 6,493,581 (“System and method for rapidrecruitment of widely distributed easily operated automatic externaldefibrillators”).

Referring again to FIG. 18, extensive operation 82 describes signaling adecision whether or not to cause the first unmanned aerial device torecognize an alias identifying the first unmanned aerial device as anautomatic and conditional response to an indication of the firstunmanned aerial device participating in the first task, the alias beingdifferent than a primary digital identifier of the first unmanned aerialdevice (e.g. control unit 860 transmitting a command 481 that configuresname recognition module 810 to respond to an alias 871 of “Aunt” as anautomatic and conditional response to control unit 860 receiving anacceptance or confirmation 381 indicating that UAD 801 will participatein delivery task 491). This can occur, for example, in a context inwhich “Aunt” is not a primary identifier 811 (serial number or InternetProtocol address, e.g.) that UAD 801 ordinarily responds to and in whichname recognition module 810 was previously configured not to respond to“Aunt”; in which a name recognition module 820 of UAD 802 responds to analias 822 of “Hulk” pursuant to the same delivery task 491; in which aprimary identifier 821 of UAD 802 is neither “Hulk” nor “Aunt”; in whichenlistment module 133 also causes alias 871 to be transferred into aparticipant list 885 of the delivery task 491 (in a met needs list 880thereof, e.g.) that grows with each successful recruitment; and in whichthe primary digital identifier would otherwise have to be usedthroughout the task in addressing UAD 801. Alternatively oradditionally, a primary unit 110 (residing in station 520, e.g.)remotely controlling UAD 801 may include a name recognition module 146configured to perform operation 84 (pursuant to a successful recruitmentas described above, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for name recognition (determining whether an incoming signalis addressing an entity by comparing a component of the incoming signalagainst one or more names of the entity, e.g.) without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,135,764 (“Configurationmanagement server, name recognition method and name recognitionprogram”); U.S. Pat. No. 7,865,356 (“Method and apparatus for providingproper or partial proper name recognition”); U.S. Pat. No. 7,822,988(“Method and system for identity recognition”); U.S. Pat. No. 7,792,837(“Entity name recognition”); U.S. Pat. No. 7,370,078 (“Determining aremote device name”); U.S. Pat. No. 6,052,682 (“Method of and apparatusfor recognizing and labeling instances of name classes in textualenvironments”).

Another system 9 in which one or more technologies may be implemented isshown in FIG. 9, depicting UAD 901 (comprising primary unit 110, e.g.)operably connected with one or more networks 190 (comprising network990, e.g.) via a wireless communication linkage 994. Network 990includes (a memory 395 or other data handling medium 195 containing) oneor more records 961, 962, 963, 964, some of which may (optionally)include digitally represented delivery tasks 980 or other tasks 491-499,each of which may (optionally) comprise one or more instances of taskdescriptions 981 or tracking modes 982 as shown. UAD 901 may(optionally) include one or more instances of tracking control modules977; record generation modules 978, or record omission modules 979. Insome contexts, UAD 901 (implementing UAD 501, e.g.) may be configured tofly (along respective paths 581, 582, 583, e.g.) among two or morestations 930, 940, 950 (e.g. on respective buildings 935, 945, 955),some or all of which may be observable by a stationary or pivotablecamera 936 (in a configuration like systems 3-8 described above, e.g.).

With reference now to FIG. 19, shown is a high-level logic flow 19 of anoperational process. Intensive operation 55 describes obtaining atracking mode of a delivery task of a first unmanned aerial device (e.g.tracking control module 977 receiving a tracking mode 982 of zeropertaining to a delivery task 980 that has been assigned to UAD 901).This can occur, for example, in a context in which a task description981 of delivery task 980 indicates a physical delivery of a “first” item(envelope 551, e.g.) to station 940; in which UAD 901 implements aprimary unit 110 that includes data acquisition module 138; in which oneor more just-completed task 493 involved UAD 901 visiting station 950;in which a tracking mode 982 of zero corresponds to a delivery protocol417 by which the specific item is delivered in lieu of operation 53(without notifying a provider of an item delivered, e.g.); and in whichtracking control module 977 would otherwise trigger data acquisitionmodule 138 to obtain at least some delivery-indicative data 411-413 inresponse to the item being delivered to station 940 (by performingoperation 53, e.g.). See FIG. 15. In some variants, for example, task493 may include one or more instances of delivery tasks 494, pickuptasks 495, recharge tasks 496, reconfiguration tasks 497, or datatransfer tasks 498. In some variants, for example, UAD 901 downloadseach successive task in a resting state after completing the prior task.Alternatively or additionally, tracking control module 977 may beconfigured to implement a default tracking mode 361—indicating at leastone of the first item(s) or UAD(s), e.g.—for each task 494-499 exceptwhen that task specifies an alternative tracking mode (such as a briefmode 362 or user-defined mode 363, e.g.).

In some variants, one or more instances of tracking control module 148resident in network 990 may be configured to perform operation 55. Thiscan occur, for example, in a context in which the first UAD 901 does nothave any on-board capability of performing operation 55 or is currentlyconfigured not to perform operation 55; in which network 990 containsone or more instances of primary unit 110 (resident in a “second” UAD202 or tower-based station 520, e.g.); and in which tracking controlmodule 148 receives tracking mode 982 as a component of a delivery task980 assigned to the first UAD 901.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for tracking control (identifying and updating how incrementsof task progress are documented, e.g.) without undue experimentation orfor configuring other decisions and devices as described herein. See,e.g., U.S. Pat. No. 8,179,261 (“Identification and surveillance device,system and method for individual item level tracking”); U.S. Pat. No.8,179,253 (“Location and tracking system, method and device usingwireless technology”); U.S. Pat. No. 8,135,171 (“Multipoint trackingmethod and related device”); U.S. Pat. No. 8,115,625 (“Parental alertand child tracking device which determines if a child has deviated froma predicated travel route”); U.S. Pat. No. 8,014,917 (“Apparatus fortracking and recording vital signs and task-related information of avehicle to identify operating patterns”); U.S. Pat. No. 7,978,065(“Device, system and method for tracking mobile assets”); U.S. Pat. No.7,951,046 (“Device, method and computer program product for tracking andmonitoring an exercise regimen”); U.S. Pat. No. 7,451,445 (“Mechanismfor tracking the execution progress of a parent task which spawns one ormore concurrently executing child tasks”); U.S. Pat. No. 7,401,030(“Method and system for tracking disposition status of an item to bedelivered within an organization”); U.S. Pat. No. 6,604,124 (“Systemsand methods for automatically managing work flow based on tracking jobstep completion status”); U.S. Pat. No. 6,463,420 (“Online tracking ofdelivery status information over a computer network”).

Referring again to FIG. 19, extensive operation 81 describes signaling adecision whether or not to omit a record of the first unmanned aerialdevice completing the delivery task of the first unmanned aerial deviceas an automatic and conditional response to the tracking mode of thedelivery task of the first unmanned aerial device (e.g. selectiveretention module 158 implementing either a decision 434 to deactivaterecord generation module 978 temporarily or a decision 435 to causerecord generation module 978 to generate a record 961 of “first” UAD 901having made such a delivery by configuring record generation module 978before UAD 901 approaches building 945). This can occur, for example, ina context in which decision 435 is “implemented” by a selectiveretention module 158 (resident in network 990, e.g.) transmitting (torecord generation module 978, e.g.) either (1) a Boolean expression(“yes,” e.g.) indicating that a user has requested one or more records961-963 of the delivery or (2) an identifier 444 of which tracking mode361-363 to use in such acquisition. Alternatively or additionally,decision 435 may be implemented by causing record generation module 978to be transmitted to or updated aboard UAD 901. Likewise a decision 434“to omit a record” may be “implemented” by selective retention module158 causing a selective deletion of record 961 (of UAD 901 deliveringthe “first” item to station 940, e.g.) before one or more similarrecords 962-964 (relating to other tasks, e.g.) are transmitted from UAD901 to network 990 (in a batch transfer, e.g.). This can occur, forexample, in a context in which a data acquisition module 139 residing inUAD 901 generates and holds at least one photograph 553, 554 or otherrecord 961-963 for each delivery aboard UAD 901 (in a memory 395 orother data-handling medium 195 thereof, e.g.); in which record omissionmodule 979 selectively deletes a subset of such records 961-963identified by selective retention module 158; and in which a remainder(comprising record 962, e.g.) of such records is later transmitted tonetwork 990. In other contexts a selective retention module 158 residentin network 990 can implement a decision to omit such a record 961 of thedelivery task completion (from a data transmission to a station 520outside network 990, e.g.) by explicitly listing (a) one or more records962-963 to be included in such transmission or (b) one or more records961 to be excluded from such transmission. This can occur, for example,in a context in which UAD 901 implements primary unit 110 and one ormore of the above-described UAD's and in which either (1) unwantedtracking of delivery task 980 would occur or (2) UAD 901 would be unableto track a completion of other potentially available tasks 491-499.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for selective event tracking without undue experimentation orfor configuring other decisions and devices as described herein. See,e.g., U.S. Pat. No. 8,219,572 (“System and method for searchingenterprise application data”); U.S. Pat. No. 8,165,932 (“Enhancement ofnetwork accounting records”); U.S. Pat. No. 8,019,771 (“Method fordynamically finding relations between database tables”); U.S. Pat. No.7,922,088 (“System and method to automatically discriminate betweendifferent data types”); U.S. Pat. No. 7,903,839 (“Method for cancelingimpact of physical property variability on image quality performance ofdigital imaging system”); U.S. Pat. No. 7,883,013 (“Mobile image captureand processing system”); U.S. Pat. No. 7,870,012 (“Method for managing aworkflow process that assists users in procurement, sourcing, anddecision-support for strategic sourcing”); U.S. Pat. No. 7,835,971(“Method and system configured for facilitating management ofinternational trade receivables transactions”); U.S. Pat. No. 7,792,808(“More efficient search algorithm (MESA) using virtual searchparameters”); U.S. Pat. No. 7,769,644 (“Bill of lading transmission andprocessing system for less than a load carriers”); U.S. Pat. No.7,739,096 (“System for extraction of representative data for training ofadaptive process monitoring equipment”); U.S. Pat. No. 7,733,223(“Effectively documenting irregularities in a responsive user'senvironment”); U.S. Pat. No. 7,631,065 (“System, method and computerprogram product for merging data in a network-based filtering andaggregating platform”); U.S. Pat. No. 7,496,670 (“Digital assetmonitoring system and method”); U.S. Pat. No. 7,467,122 (“System foraiding the design of product configuration”); U.S. Pat. No. 7,394,817(“Distributed data caching in hybrid peer-to-peer systems”); U.S. Pat.No. 7,346,675 (“System, method and computer program product forcontract-based aggregation”); U.S. Pat. No. 7,142,110 (“Automaticconditioning of data accumulated by sensors monitoring supply chainprocesses”).

FIG. 10 depicts another context in which one or more of theabove-described systems may be implemented. System 10 comprises one ormore instances of participating mobile devices 1010 such as airplanes1001, helicopters 1002, or dirigibles 1003. Each such mobile device 1010may, moreover, comprise a passenger vehicle 1004 (like a car 602 orpassenger airplane, e.g.), a handheld device (like a cellular telephoneor UAD 201, UAD 202 of FIG. 2, e.g.), or another unmanned aerial device1005 (such as a glider, balloon, rocket, helicopter 1002, dirigible1003, or other such device configured to be maneuvered in flight, e.g.).In some contexts, moreover, such a device may include one or moreinstances of fuel cells 1021 or batteries or other primary energysources 1022 or secondary energy sources (a photovoltaic cell, e.g.);wireless communication linkages 1094 (operably coupled with one or morecontrollers 1095 in network 1090 and remote from device 1010, e.g.); aglobal positioning system (GPS) 1063; timers 1064; or local controllers1085 operable for controlling one, two, or several props 1071, 1072,1073 or wheels 683 (via one or more motors 1081, 1082, 1083, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for remotely, autonomously, or otherwise controlling one ormore devices in flight without undue experimentation or for configuringother decisions and devices as described herein. See, e.g., U.S. Pat.No. 8,090,525 (“Device and method for providing automatic assistance toair traffic controllers”); U.S. Pat. No. 8,078,395 (“Control system forautomatic circle flight”); U.S. Pat. No. 7,890,221 (“Method and devicefor consolidation by software synchronisation in flight controlcomputers”); U.S. Pat. No. 6,926,233 (“Automatic formation flightcontrol system (AFFCS)—a system for automatic formation flight controlof vehicles not limited to aircraft, helicopters, or space platforms”);U.S. Pat. No. 6,847,865 (“Miniature, unmanned aircraft with onboardstabilization and automated ground control of flight path”); U.S. Pat.No. 6,604,044 (“Method for generating conflict resolutions for airtraffic control of free flight operations”); U.S. Pat. No. 6,552,669(“Automated air-traffic advisory system and method”); U.S. Pat. No.6,538,581 (“Apparatus for indicating air traffic and terrain collisionthreat to an aircraft”); U.S. Pat. No. 6,526,377 (“Virtual presence”);U.S. Pat. No. 6,133,867 (“Integrated air traffic management andcollision avoidance system”).

Another system in which one or more technologies may be implemented isshown in FIG. 11. Secondary unit 1150 comprises one or more instances ofsequence recognition modules 1106, 1107; data capture modules 1108,1109; interface control modules 1110, 1111, 1112, 1113, 1114, 1115; taskimplementation modules 1130, 1131, 1132, 1133, 1134, 1135, 1136, 1137,1138, 1139; timers 1141 or other delay elements; outputs 1142 (speakers1171 or displays 1172 configured to present data to device user 226,e.g.); proximity detection modules 1153, 1154; resource reservationmodules 1156, 1157; or motion control modules 1158, 1159. In somevariants, one or more instances of secondary unit 1150 may be operablycoupled with event/condition detection unit or may reside in one or morenetworks 190, 990, 1090 described above.

Another system in which one or more technologies may be implemented isshown in FIG. 12. A medium 1200 (of storage or transmission or display,e.g.) may include one or more instances of task scheduler 1220containing or otherwise able to access table entries 1225 comprising oneor more digitally represented tasks 1211, 1212, 1213, 1214 (each shownas a row, e.g.), each of which may include one or more instances of taskidentifiers 1221, values 1222, or specifications 1223. Medium 1200 mayalso include status-indicative data 1240 (comprising one or more ofimage data 1241, GPS data 1242, or timing data 1243, e.g.); taskdescriptions 1251, 1252, 1253; or other task-related data 1250 asdescribed herein.

Another context in which one or more technologies may be implemented isshown in FIG. 13, depicting a stationary computer (implementinginterface device 310, e.g.) having a keyboard 1391 (implementing input391, e.g.) and a user's chair 1373 in an office 1380. Office 1380further comprises a desktop 1372 that supports or comprises a target1360 (an ASIC 409, surface pattern, or other feature detectable by UAD1005, e.g.) within a vicinity 1371 of which a delivery or landing (by orof UAD 1005, e.g.) may occur as described below.

Another context in which one or more technologies may be implemented isshown in FIG. 14, depicting one or more instances of articles 1400 eachcomprising a comparator 1401 or other event/condition logic 1410 thatmay (optionally) implement target 1360 as well. Alternatively oradditionally, article 1400 may comprise one or more instances of passiveradio frequency identification (RFID) chips 1461; a cup 1464 or othercontainer 1465 above which is a position 1463 to which UAD 1005 may fly;device activations modules 1471, 1472; device configuration modules1475; task implementation modules 1481, 1482, 1483, 1484, 1485, 1486;device configuration modules 1475; task implementation modules 1481,1482, 1483, 1484, 1485, 1486; charge-coupled devices (CCD's) 1493 orother sensor arrays 1494; or disk drives 1495. In some contexts, asvariously described herein, article 1400 (implementing UAD 1005, e.g.)may include a sensor array 1494 (camera, e.g.) configured to depict(some or all of) a vicinity (chair 1373, e.g.) of an object (target1360, e.g.) or a person 727 or of itself.

Another context in which one or more technologies may be implemented isshown in FIG. 20, depicting various structures forming a part of UAD1005 (on a bottom or side thereof, e.g.) having one or more mechanicallinkages 2040 (adhesives or tethers or clamps or other such releasablesupport mechanisms 2020, e.g.) that can physically engage or disengageone or more cargo modules 2090. As shown, each such cargo module 2090may include one or more instances of packages 2050 (having a hole 2049therethrough, e.g.); syringes 2061, inhalers 2062, capsules 2063(containing a dose 2064 of therapeutic material, e.g.), or other suchproducts 2060 (in a dispenser 2038, e.g.); data handling units 2078(comprising a camera 2071, display 2072, or other device having aprimary function of handling data, e.g.); or releasable UAD energysources (battery 2085, e.g.). In a variant of structure 2030 configuredto engage package 2050, for example, a cross-sectional view 2048 acrosshole 2049 is shown in a context in which package 2050 protrudes into agroove 2026 of UAD 1005. Post 2006 may be moved (e.g. magnetically by asolenoid or mechanically by a spring, not shown) toward recess 2023 (tothe right, as shown) to engage package 2050 or away from recess 2023 (tothe left, as shown) to disengage package 2050, as described below.Alternatively or additionally, UAD 1005 may include a robotic arm 2039or similar structure 2030 for engaging or disengaging cargo module 2090(pursuant to an engagement trigger or disengagement trigger from of oneor more task implementation modules 1130-1139, 1481-1486, e.g.).

In some embodiments, a material is “therapeutic” if it includes apharmaceutical (e.g. an antibiotic, pain reliever, or stimulant), anutraceutical (e.g. a dietary supplement or other therapeutic foodingredient), a topically applied material (e.g. a liniment or lotionprescribed or used in a medical other health-related practice), or otherproduct or components (e.g. propellants, inhalants, inoculants, orresorbable binders or coatings) intended primarily to maintain orimprove a subject's health or performance. Some embodiments relate to adelivery of a “single dose” (±50%, e.g.) generally signifying aprescribed or recommended amount of a material (“two aspirin,” e.g.) tobe administered into or onto a subject's body either (1) periodically or(2) at one time.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for configuring devices to engage or disengage data handlingunits, medical products, energy sources, or other such modular cargowithout undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,192,698(“Sampling probe, gripper and interface for laboratory sample managementsystems”); U.S. Pat. No. 8,179,496 (“Display casing capable ofaccommodating LCD panel modules of different sizes”); U.S. Pat. No.8,167,236 (“Hybrid lift air vehicle”); U.S. Pat. No. 8,164,302 (“Systemfor replenishing energy sources onboard different types of automaticvehicles”); U.S. Pat. No. 8,141,814 (“Lighter-than-air vertical loadlifting system”); U.S. Pat. No. 8,128,026 (“Removable cargo pod withlifting mechanism and open top”); U.S. Pat. No. 8,122,982 (“Mobile robotsystems and methods”); U.S. Pat. No. 8,101,434 (“Method for LED-moduleassembly”); U.S. Pat. No. 8,091,463 (“Machine gun ammunition holderincorporating center of gravity downward ejection-deflector”); U.S. Pat.No. 8,066,460 (“Apparatus and method for cargo loading system”); U.S.Pat. No. 8,037,839 (“Device for handling a load hoisted between twolocations offset both vertically and horizontally”); U.S. Pat. No.8,029,228 (“Cable hoisting apparatus”); U.S. Pat. No. 7,919,060(“Dispenser for flattened articles”); U.S. Pat. No. 7,913,370 (“Methodand apparatus for assembling exterior automotive vehicle body componentsonto an automotive vehicle body”); U.S. Pat. No. 7,750,778 (“System andmethod for attachment of objects”); U.S. Pat. No. 7,717,255 (“End of armtool, apparatus, and method of engaging an article”); U.S. Pat. No.7,648,513 (“Surgical manipulator for a telerobotic system”); U.S. Pat.No. 7,641,461 (“Robotic systems for automated construction”); U.S. Pat.No. 7,549,204 (“Methods for picking and placing workpieces into smallform factor hard disk drives”); U.S. Pat. No. 7,474,212 (“Object taggedwith RFID tag and device and method for processing it”); and U.S. Pat.No. 7,252,453 (“Robot arm coupling apparatus”).

Another context in which one or more technologies may be implemented isshown in FIG. 21. A medium 2100 (configured to implement storage ortransmission or display, e.g.) may bear one or more instances ofindications 2101, 2102, 2103, 2104, 2105, 2106, 2107, 2108, 2109;triggers 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119, 2120;guidance 2130; decisions 2131, 2132, 2133; clips 2151, 2152, 2153;images 2161, 2162, 2163, 2164, 2165; distances 2171, 2172, 2173, 2174,2175; directions 2186, 2187, 2188, 2189; or signals 2191, 2192, 2193,2194, 2195. Each of these items may (optionally) include two or morecomponents. In various embodiments, for example, one or more of triggers2111-2120 may comprise one or more instances of a character sequence2121 or similar digital expression 2122 (expressing a scalar operatingparameter 2127, an alphanumeric identifier, or other such operatingparameter 2128, e.g.) to which a trigger recipient (an instance of taskimplementation module 1130 residing in UAD 1005 or another moduledepicted in FIGS. 1-20, e.g.) is configured to respond. Each suchtrigger may likewise comprise one or more software-implemented controlmodules 2124 (comprising a command sequence 2125 executable by processor365, e.g.) or operating parameters 2126, 2127, 2128.

Several variants described herein refer to software or otherdevice-detectable “implementations” such as one or more instances ofcomputer-readable code, transistor or latch connectivity layouts orother geometric expressions of logical elements, firmware or softwareexpressions of transfer functions implementing computationalspecifications, digital expressions of truth tables, or the like. Suchinstances can, in some implementations, include source code or otherhuman-readable portions. Alternatively or additionally, functions ofimplementations described herein may constitute one or moredevice-detectable outputs such as decisions, manifestations, sideeffects, results, coding or other expressions, displayable images, datafiles, data associations, statistical correlations, streaming signals,intensity levels, frequencies or other measurable attributes, packets orother encoded expressions, or the like from invoking or monitoring theimplementation as described herein.

In some embodiments, a “state” of a component may comprise “available”or some other such state-descriptive labels, an event count or othersuch memory values, a partial depletion or other such physical propertyof a supply device, a voltage, or any other such conditions orattributes that may change between two or more possible valuesirrespective of device location. Such states may be received directly asa measurement or other detection, in some variants, and/or may beinferred from a component's behavior over time. A distributed or othercomposite system may comprise vector-valued device states, moreover,which may affect dispensations or departures in various ways asexemplified herein.

Another system in which one or more technologies may be implemented isshown in FIG. 22. A medium 2200 (of storage or transmission or display,e.g.) may include one or more instances of positions 2230 (described bya respective X-ordinate 2231 and Y-ordinate 2232, e.g.). In somecontexts, such positions can each be described by other coordinates aswell: a Z-ordinate 2233 (altitude, e.g.) or an angle 2234 (in a polarcoordinate system, e.g.). In some contexts, locations 2240 describedherein may likewise be expressed in words or numbers, such as one ormore addresses 2235, 2236 or distances 2237, 2238, 2239. In variouscontexts, an entity herein may likewise be described by one or morenames 2241, 2242, 2243, 2244, 2245, 2246; account numbers 2249; or othersuch descriptors 2250, 2251, 2252, 2253, 2254. Sets of entities may beidentified by one or more lists 2261, 2262, 2263, 2264 on medium 2200.In some contexts, for example, such media 2200 may comprise one or moretags 2267, 2268; barcodes 2271; or other labels 2275 as furtherdescribed below.

Another system in which one or more technologies may be implemented isshown in FIG. 23. A medium 2300 (of storage or transmission or display,e.g.) may include one or more instances of values 2311, 2312, 2313; dataanomalies 2315; or other data 2321, 2322, 2323, 2324, 2325, 2326, 2330as described below. In some contexts, medium 2300 may likewise containone or more instances of thresholds 2331, 2332, 2333; intervals 2341,2342; device-detectable phenomena 2354; messages 2356, 2357;authorizations 2358; images 2371, 2372, 2373, 2374, 2375, 2376, 2377;times 2381, 2382, 2383, 2384, 2385, 2386, 2387, 2388; or criteria 2390,2391, 2392, 2393, 2394, 2395, 2396, 2397, 2398, 2399. Some or all ofthese may be expressed digitally. In some contexts, moreover, a medium2300 (of display, e.g.) may present one or more menus 2370 comprisingone or more default selections 2361 or other selections 2362, 2363,2364, 2365, 2366 (for a UAD operator 729 to choose among, e.g.).

Another system in which one or more technologies may be implemented isshown in FIG. 24. A medium 2400 (of storage or transmission or display,e.g.) may include one or more instances of indications 2401, 2402, 2403,2404, 2405, 2406, 2407, 2408; triggers 2411, 2412, 2413, 2414, 2415,2416; or other signals 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428.In some contexts, medium 2400 may likewise contain one or morefrequencies 2431, 2432, 2441, 2442 or ranges 2435, 2445 thereof; results2451, 2452, 2453 of actions; instances of code 2461, 2462, 2463(executable by processor 365, e.g.); definitions 2471, 2472, 2473, 2474,2475; ranges 2455, 2465, 2475; or other thresholds. Some or all of thesemay be expressed digitally.

Another system in which one or more technologies may be implemented isshown in FIG. 25. A detection unit 2500 may include one or moreinstances of timers 2521, 2522, 2523, 2524, 2525; interrogation modules2530; cameras 2541 or other optical sensors 2545; microphones 2552;carbon monoxide sensors 2553, smoke sensors 2554, or other concentrationsensors; or heat sensors 2555 or other such sensors 2560 (for detectingintrinsic properties of matter, e.g.).

Another system in which one or more technologies may be implemented isshown in FIG. 26. A disablement device 2690 (of a component of a UAD orother device described herein, e.g.) may include one or more instancesof releasable adhesives 2681 or flammable compounds; bullets or othermissiles 2682; throwable nets or lines 2683 (incorporating weights 2684,e.g.); electromagnetic pulse generators; or other such componentsconfigured to disable a UAD or other entity as described herein. In somecontexts, for example, a stationary or other device (UAD, e.g.) may beconfigured to incorporate one or more such disablement devices 2690 (asa cargo module 2085 or other component, e.g.) to impede access into aregion (room or proximity or other zone, e.g.) by at least partlydisabling another entity in response to one or more triggers 2414described herein.

Another system in which one or more technologies may be implemented isshown in FIG. 27. A stationary structure 2750 may include one or moreinstances of windows 2709, doors 2742, or other movable actuators 2710.In a context in which stationary structure 2750 comprises a parked car2702, for example, one or more windows 2709 may be opened by windowcontrol motor 2701. Alternatively or additionally, in some contexts,stationary structure may comprise one or more platforms 2725, towers2730, or buildings 2745 (sometimes having one or more apertures 2741,e.g.) as described below.

Another context in which one or more technologies may be implemented isshown in FIG. 35. System 3500 includes data handling unit 3550, one ormore of which may (optionally) comprise primary unit 110,event/condition detection unit 400, or secondary unit 1150. Each datahandling unit 3550 may comprise one or more differences 3520; protocols3531, 3532, 3533, 3534; decisions 3540, 3541, 3542, 3543, 3544, 3545,3546, 3547, 3548, 3549; sensors 3551, 3552, 3553; or pseudorandom numbergenerators 3570 or other inputs 3581, 3582, 3583, 3584, 3585. Datahandling unit 3550 may likewise comprise one or more processors 3565configured to perform various software-implemented tasks, in somecontexts, such as identifying one or more patterns 3591, 3592, 3593 thatmay be present in responses 3590 as described below.

FIG. 36 depicts another context in which one or more technologies may beimplemented. System 3600 comprises a primary unit 3610 that may includeone or more instances of pattern recognition modules 3630, 3631, 3632,3633, 3634, 3635, 3636, 3637, 3638, 3639; location detection modules3641, 3642, 3643; flight control modules 3651, 3652, 3653, 3654;navigation modules 3661, 3662; decision modules 3671, 3672, 3673, 3674,3675, 3676; or signal detection modules 3681, 3682, 3683, 3684, 3685,3686 as described in further detail below. In some contexts, primaryunit 3610 may be operably coupled to one or more networks 190, 3690 viaone or more communication linkages 3694. Instances of storage or otherdata-handling media 3695 operably coupled to one or more such modulesmay, moreover, reside in primary unit 3610 or network 3690, as describedbelow. In some contexts, moreover, primary unit 3610 may implement (aninstance of) primary unit 110.

FIG. 37 depicts another context in which one or more technologies may beimplemented. System 3700 comprises a secondary unit 3750 that mayinclude one or more instances of operator interfaces 3711, 3712, 3713;proximity detection modules 3721, 3722; checksums 3731, 3732;comparators 3741, 3742; task implementation modules 3751, 3752, 3753,3754; identification modules 3761, 3762; estimation modules 3771, 3772;data distillation modules 3781, 3782, 3783, 3784; or data aggregationmodules 3791, 3792 as further described below. In some contexts,moreover, secondary unit 3750 may implement secondary unit 1150.

Another system in which one or more technologies may be implemented isshown in FIG. 28. A house 2845 sits upon a parcel 2840 of land adjacenta sidewalk 2848. In some contexts an unmanned aerial device 2801(comprising one or more owner identifiers 2865 or operator identifiers2866, e.g.) approaches the house 2845 (pursuant to one or more tasksdescribed herein, e.g.) and encounters another UAD 2802 (following apatrol route 2878 or other path, e.g.).

With reference now to FIG. 38, shown is a high-level logic flow 38 of anoperational process. Intensive operation 64 describes obtaining adescriptor of a first entity operating a first unmanned aerial device(e.g. operator interface 3711 receiving an owner identifier 2865 oroperator identifier 2866 indicating who is operating or managing theoperation of UAD 2801). This can occur, for example, in a context inwhich operator identifier 2866 comprises a user name 2243, facility name2244, corporate entity name 2245, or account number 2249 used for suchdescription and in which UAD 2801 implements UAD 1005. In some contexts,for example, corporation or other entity operating UAD 2801 may chooseto identify itself by one or more hardware or software identifiers (acontroller name 2246, e.g.) or by one or more locations 2240 (of a house2845 or parcel 2840 of land, e.g.). In some variants such locations 2240may comprise a street address 2236 other expressions of distances 2238from a reference position (mile markers, e.g.). Alternatively oradditionally, operation 64 may be performed by an identification module3761 configured to assign a default descriptor 2253 to UAD 2801 untiland unless identification module 3762 receives a wireless signal 2425containing an operator identifier 2866.

Intensive operation 67 describes obtaining an operatorship criterion(e.g. pattern recognition module 3631 implementing one or more criteria2392-2396 applicable to one or more corresponding descriptors2250-2254). This can occur, for example, in a context in which criterion2396 is satisfied for any descriptor that is present in a first list2261; in which criterion 2392 is satisfied for any descriptor that ispresent in a second list 2262; in which criterion 2393 is satisfied forany descriptor (expressed as a sequence 2121 of characters, e.g.)satisfying a checksum 3731 or cyclical redundancy check (of digitalvalues each corresponding to each character, e.g.) or similarmathematically expressed requirement; in which each such criterion willotherwise not be satisfied; and in which pattern recognition module 3631can invoke any such criteria selectively. In some variants, for example,such criteria are each implemented in an instance of code 2462executable by processor 365 or other structure operably accessible toprimary unit 3610.

Extensive operation 72 describes signaling a decision whether or not toimpede the first unmanned aerial device entering a particular region asan automatic and conditional result of applying the operatorshipcriterion to the descriptor of the first entity operating the firstunmanned aerial device (e.g. task implementation module 3754implementing a decision 3545 to prevent UAD 2801 from entering house2844 partly based on location detection module 3642 determining that UAD2801 is flying over parcel 2840 and partly based on pattern recognitionmodule 3631 failing to recognize an operator identifier 2866 receivedfrom UAD 2801). This can occur, for example, in a context in which sucha decision 3545 is implemented by invoking a flight control module 3654configured to cause UAD 2802 to block UAD 2801 from moving closer tohouse 2844; in which task implementation module 3754 would not otherwiseimplement such a decision 3545; and in which one or more such criteria2392-2396 have previously been selected (as a corresponding selection2362-2366 on menu 2370, e.g.) by an occupant or administrator of theparticular region (a building 935 or office 1380 or parcel 2840 of land,e.g.). In some contexts, moreover, task implementation module 3754 maybe configured to respond to such circumstances by implementing adecision 3546 to cause UAD 2802 to collide with or otherwise interceptor disable UAD 2801.

Another instance of stationary structure 2750 is shown in FIG. 29. Asystem 29 comprising a camera 2918 and other circuitry is configured tomonitor a vicinity 2955 of an opening 2942 of a garage 2936. Suchcircuitry (controller 2910, e.g.) controls a door 2941 of the garage2936 within a range 2943 of its motion via a motor 2925 thereof, limitedto patentable subject matter under 35 U.S.C. 101. In some variants, suchcircuitry further comprises one or more limited-range transceivers 2911,antennas 2912, or other sensors 2915; proximity detection modules 2921;or pattern recognition modules 2922. In some contexts, a UAD 2905 may beconfigured to enter or exit garage 2936 via opening 2942. In somevariants, such UAD (implementing UAD 1005, e.g.) may include one or morebarcodes 2961, UAD identifiers 2962, radio frequency identification(RFID) tags 2963, or authorization codes 2964 as described below.

With reference now to FIG. 39, shown is a high-level logic flow 39 of anoperational process. Intensive operation 63 describes detecting a firstunmanned aerial device being within a vicinity of a portal (e.g.interrogation module 2530 detecting a response 3590 from UAD 2905 in avicinity 2955 of garage door 2941). This can occur, for example, in acontext in which controller 2910 includes detection unit 2500 and datahandling unit 3550 and resides in or on garage 2936; in which UAD 2905includes an RFID tag 2963 that is responsive to interrogation module2530; and in which the vicinity 2955 is a range within whichinterrogation module 2530 can trigger RFID tag 2963 to transmit theresponse D958 and within which antenna 2912 can detect the response D958from UAD 2905. In some contexts, for example, RFID tag 2963 may be apassive tag so that response D958 is powered entirely by interrogationmodule 2530.

Intensive operation 61 describes obtaining an indication of an identityof the first unmanned aerial device (e.g. optical pattern recognitionmodule 2922 detecting a primary identifier 821 or alias 822 identifyingUAD 802 on a label 2275 or other printed content on UAD 802). This canoccur, for example, in a context in which such a label 2275 is affixedto UAD 802; in which UAD 802 includes primary module 3610 and implementsthe “first” UAD 2905; and in which optical pattern recognition module2922 performs such processing upon image data 1242 depicting UAD 2905(obtained via one or more cameras 2541, 2918, e.g.). Alternatively oradditionally, operation 61 may be performed by a pattern recognitionmodule 3639 generating a null or default name 2241 that initiallyidentifies the “first” UAD 2905 (before receiving an identifier in realtime, e.g.) or by the “first” UAD receiving a UAD identifier 2962 (on abarcode 2961, e.g.) that identifies it. Alternatively or additionally,in some implementations, signal detection module 3682 may performoperation 61 by receiving a wireless signal 2426 containing the identityindication 2402 (a serial number or other UAD identifier 2962, e.g.). Insome variants, moreover, signal 2426 may include additional data(status-indicative data 1240 or an authorization code 2964, e.g.) aswell.

Extensive operation 75 describes signaling a decision whether or not toallow an actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of the portal(e.g. decision module 3675 transmitting a negative decision 3541 ifpattern recognition module 3631 recognizes the primary identifier 821 oralias 822 identifying a UAD 802 that is within a vicinity 2955 of anentry of garage 2936). This can occur, for example, in a context inwhich the “actuator” comprises garage door 2941 and in which the“negative” decision 3541 is a decision (a) to raise garage door 2941 or(2) not to lower garage door 2941, either such action having the effectthat the portal (opening 2942, e.g.) will not be obstructed (closed,e.g.). In some contexts, moreover, decision module 3675 may beconfigured to trigger the garage door 2941 to rise only partly and thenimmediately to close. This can occur, for example, in a context in whichtask implementation module 3752 triggers such closure in response to anindication that garage door 2941 has opened by ⅓ of its range 2943 or inresponse to sensor 2915 detecting that UAD 2905 has passed through or inresponse to timer 2522 detecting that 2 seconds have passed sinceoperations 61 & 63 were complete (and that UAD 2905 has therefore had anadequate opportunity to pass through opening 2942, e.g.).

Another system in which one or more technologies may be implemented isshown in FIG. 30. A wall 3020 may comprise an interior or exteriorstructure of an office 1380, house 2845, garage 2936, or other facilitydescribed below. A base 3010 mounted onto the wall 3020 receiveselectrical power via a cord 3018 and plug 3017 which engages an outlet3019 of wall 3020. Base 3010 includes one or more prongs 3081, 3082having respective surfaces 3071, 3072 upon which a UAD 3005 may supportitself. In some variants, one or more CCD's 1493 or other sensors 3015may capture data from a vicinity of such surfaces 3071, 3072.Alternatively or additionally, UAD 3005 may be configured to perform oneor more tasks 491-499, 3091, 3092, 3093, 3094 as described herein. Insome context, for example, UAD 3005 may be configured to land, berecharged, or launch itself autonomously generally as described below(especially with reference to FIG. 31, which depicts a side view 3045 ofbase 3010, e.g.).

With reference now to FIG. 40, shown is a high-level logic flow 40 of anoperational process. Intensive operation 66 describes obtaining firstdata including optical data from a vicinity of a reference surface incontact with a first unmanned aerial device (e.g. signal detectionmodule 3681 receiving one or more images 2371 from a charge-coupleddevice 1493 or camera 4636 in a vicinity 3055 of one or more surfaces3071, 3072 of a mooring structure that support UAD 3005). This canoccur, for example, in a context in which the “first” data 2321 includessuch optical data; in which the mooring structure comprises a base 3010mounted upon a wall 3020 near the camera 4636 or other sensor-containingarticle 1400; and in which primary unit 3610 resides in UAD 3005 or base3010. In some variants, for example, article 1400 may comprise UAD 3005or base 3010.

Extensive operation 77 describes signaling a decision as an automaticand conditional response to the application of a first recognitioncriterion to the optical data from the vicinity of the reference surfacein contact with the first unmanned aerial device whether or not to causethe first unmanned aerial device to be disengaged from the referencesurface (e.g. optical pattern recognition module 3632 and decisionmodule 3671 jointly transmitting a trigger 2411 instructing UAD 3005 totake off from the reference surface as a conditional result 2451 ofoptical pattern recognition module 3632 determining that at least oneimage 2371 satisfies at least one criterion 2396 specified by operator729). This can occur, for example, in a context in which primary unit3610 includes media 2300, 2400; in which optical pattern recognitionmodule 3632 transmits result 2451 to decision module 3671; and in whichresult 2451 is a determinant by which decision module 3671 decideswhether to transmit trigger 2411. In some implementations, one or moreother triggers 2111-2120 may also be configured each as a determinant(as an input to decision module 3671, e.g.) that enables or prevents thetransmission of trigger 2411.

Intensive operation 78 describes signaling a decision as an automaticand conditional response to the application of the first recognitioncriterion to the optical data from the vicinity of the reference surfacewhether or not to cause the first unmanned aerial device to obtainsecond data with the first unmanned aerial device disengaged from thereference surface (e.g. decision module 3674 implementing a decision3542 to obtain one or more images 2372, clips, or other “second” data2322 by invoking a detection unit 2500 or other task implementationmodules 1130-1139 aboard UAD 3005 after UAD 3005 disengages from the oneor more reference surfaces 3071, 3072). This can occur, for example, ina context in which UAD 3005 includes (an instance of) primary unit 3610and secondary unit 1150; in which decision module 3674 is configured torespond directly to trigger 2411 or according to a surveillanceprotocol; and in which such “second” data 2322 would not otherwise beobtained from the vantage point of UAD 3005. In some contexts, forexample, such a protocol may include a task sequence (executed by taskimplementation module 3751, e.g.) comprising a task 3091 of invoking alocation detection module 3643 configured to generate location data 3482(indicative of a position of an apparent intruder or other anomaly 2315,e.g.) from the “first” data 2321; a task 3092 of invoking one or moreflight control modules 3651-3654 configured to navigate UAD 3005 frombase 3010 using the location data 3482; and a task 3093 of acquiring the“second” data 2322 (periodically or continuously, e.g.) during or aftersuch navigation (in flight, e.g.). This can occur, for example, in acontext in which an intruder (a device or person, e.g.) could otherwisedisable UAD 3005 (via a disablement device 2690 carried by the intruder,e.g.) before any such “second” data 2322 is acquired.

FIG. 31 depicts a proximity 3155 of UAD 3005 just having launched fromor about to land on base 3010. When UAD 3005 is docked on base 3010, arm3151 rests in contact with an upper inner surface 3071 of prong 3081. Insome contexts base 3010 includes a charging mechanism 3114 suitable forone or more corresponding features of UAD 3005. In one implementation,for example, charging mechanism 3114 comprises a coil 3122 by which acorresponding coil (not shown) in body 3190 may receive a chargingcurrent (configured to charge a battery 2085 aboard UAD 3005. This canoccur, for example, in a context in which UAD 3005 implements UAD 1005and comprises a structure 2030 for engaging battery 2085 and in whichbattery 2085 is configured to power one or more motors 1081-1083.Alternatively or additionally, UAD 3005 may be configured to permitbattery 2085 to be charged by a pair of electrical contacts 3141 onrespective arms 3151 of UAD 3005. This can occur, for example, in acontext in which charging mechanism 3114 comprises conductive surfaces3071, 3072 configured to carry a charging voltage and engage suchcontacts when UAD 3005 lands. In some variants, moreover, base 3010 mayinclude one or more sensors 3115, 3116 (comprising a camera 2541,microphone 2552, or other sensors 2560 described herein, e.g.); one ormore buttons 3160 by which operator 729 may trigger UAD 3005 (to performa surveillance or delivery task, e.g.); or other unit features describedherein.

With reference now to FIG. 41, shown is a high-level logic flow 41 of anoperational process. Intensive operation 59 describes obtaining operatorinput from an operator of a first unmanned aerial device as an earlierinput component (e.g. operator interface B660 receivingdevice-executable code 2461 as input 3583 from a programmer or otheroperator 729 of UAD 3005 on “day zero”). This can occur, for example, ina context in which operator 729 has physical access to an operatorinterface 3713 (a mode control switch or button 3160, e.g.) of base3110; in which UAD 3005 can receive such device-executable code 2461 (asan upgrade or patch, e.g.) directly via an electrical conduit (contact3141, e.g.) or otherwise while docked on base 3010; and in which UAD3005 includes a processor 365 configured to cause UAD 3005 to performone or more tasks 491-499, 3091-3093 implemented within such code 2461.In some contexts, for example, such code defines one or more automaticor other triggers 2111-2119, 2411-2416 configured to cause such taskperformance to begin. Alternatively or additionally, such input 3583 caninclude task implementation modules 1130-1139 installed into UAD 3005earlier (during manufacture, e.g.).

Intensive operation 56 describes obtaining environmental sensor inputfrom a vicinity of the first unmanned aerial device as a later inputcomponent (e.g. heat sensor 2555 generating thermal data 2324 indicatingan indoor fire in a vicinity 3055 of UAD 3005 as “later” environmentalsensor input 3585 one or more days after “day zero”). This can occur,for example, in a context in which secondary unit 3750 implements medium2400 and data handling unit 3550; in which primary unit 3610 implementsevent/condition detection unit 400; in which base 3010 includes one orboth of primary unit 3610 and secondary unit 3750; in which detectionunit 2500 resides in either UAD 3005 or base 3010; and in whichcomparator 3741 detects whether thermal data 2324 exceeds a thermalthreshold 2333 as a trigger 2415 for a task implementation moduledescribed herein (configured to invoke flight control module 3651,e.g.).

Extensive operation 71 describes signaling a decision without regard toany other operator input whether or not to launch the first unmannedaerial device partly based on the operator input from the operator ofthe first unmanned aerial device obtained as the earlier input componentand partly based on the environmental sensor input from the vicinity ofthe first unmanned aerial device obtained as the later input component(e.g. flight control module 3651 causing UAD 3005 to launch in responseto particular sensor input 3585 irrespective of whether any operators729 of UAD 3005 provide further input 3584 after the “day zero” operatorinput 3583). This can occur, for example, in a context in which the “dayzero” operator input 3583 configures a task implementation module 3753of UAD 3005 to be (potentially) triggered by sensor input 3585indicative of fire by generating a fire-indicative trigger 2415, 2416 inresponse to which flight control module 3651 launches UAD 3005; in whichsuch sensor input 3585 is received from one or more cameras 2541 orother optical sensors 2545 or microphones 2552 or carbon monoxidesensors 2553 or smoke sensors 2554 or heat sensors 2555; and in which nofurther operator input 3584 (after the “day zero” input) is received. Insome contexts, moreover, task implementation module 3753 may beconfigured to disregard or otherwise do without further operator input3584 (confirmations, e.g.) received via operator interface B660. In somevariants, moreover, UAD 3005 may be configured to investigate thepremises (a room or house 2845 including vicinity 3055, e.g.) andtransmit data 2325 acquired via a sensor 3015 aboard UAD 3005 (aswireless signal 2422, e.g.) within a few minutes after such launch.

FIG. 32 depicts a context in which one or more technologies may beimplemented. A first entity 3201 (UAD 1005, e.g.) may follow a path 3270through a sequence of positions 3241, 3242, 3243. Each position 3241 maybe described with reference to corresponding coordinates 3221, 3222,3223 in a coordinate system (featuring at least an X-axis 3221 and aY-axis 3222, e.g.). In some contexts, entity 3201 can detect or bedetected by a second entity 3202 (via one or more energy signature paths3271, 3272 along which light or sound may travel, e.g.) which detectionmay affect which path 3271, 3272 entity 3201 will follow subsequently.

With reference now to FIG. 42, shown is a high-level logic flow 42 of anoperational process. Intensive operation 58 describes obtaining firstdata including an X-ordinate of a first location and a Y-ordinate of thefirst location indicating a first entity moving from the first locationto a second location (e.g. global positioning system 1063 generating GPSdata 3481 that signals position 3241 and an indication 2405 of entity3201 moving southward). This can occur, for example, in a context inwhich distillation unit 3480 is operably coupled with entity 3201; inwhich position 3241 is the “first” location; in which the “first” entity3201 comprises a helicopter 1002 or other mobile device 1010 describedabove; in which data 3481 includes an instance of longitude (X-ordinate2231, e.g.) and latitude (Y-ordinate 2232, e.g.) and altitude(Z-ordinate 2233, e.g.); and in which indication 2405 signals aparticular location (position 3242 or a waypoint thereof, e.g.) orheading or apparent direction of travel.

Intensive operation 60 describes obtaining second data indicative of adevice-detectable energy signature path having existed between a secondentity and the first location (e.g. signal detection module 3683recognizing a radio frequency signal 2423 or optical signal 2424transmitted by entity 3202 and received by entity 3201). This can occur,for example, in a context in which entity 3201 includes one or moreantennas 455 that receive RF signal 2423 or optical sensors 2545 thatreceive optical signal 2424 via path 3271; in which path 3271 issufficiently direct to permit such wireless signal travel; and in whichone or more such signals 2423, 2424 are strong enough to be detectablewhen received at position 3241. In some contexts, for example, entity3201 includes both an antenna 455 and an optical sensor 2545 so thatoperation 60 may occur even in a context in which path 3271 is onlypermeable to one of these signals 2423, 2424. Alternatively oradditionally, (an instance of) primary detection module 3610 may resideaboard entity 3201.

Intensive operation 62 describes obtaining third data indicative of nodevice-detectable energy signature path having existed between thesecond entity and the second location (e.g. signal detection module 3684recognizing a failure to detect radio frequency signal 2423 or opticalsignal 2424 transmitted by entity 3202 at position 3242). This canoccur, for example, in a context in which entity 3201 includes one ormore antennas 455 configured to receive RF signal 2423 except for thefact that no suitable RF signal path exists from entity 3202 to position3242. In some contexts, for example, operation 62 can occur (because ofa blocked or other unsuccessful transmission from entity 3202, e.g.)after several instances of operation 60 (resulting from successfultransmissions from entity 3202, e.g.) have occurred. Alternatively oradditionally, signal detection module 3684 can perform operation 62 in acontext in which entity 3201 includes one or more optical sensors 2545configured to receive optical signal 2424 except for the fact that nosuitable optical signal path exists from entity 3202 to position 3242.(It will be understood that even if gamma radiation were intentionallytransmitted westward toward position 3242, the path 3272 along which ittravels is not a “device-detectable energy signature path” unless one ormore devices are configured to detect it.)

Extensive operation 76 describes causing the first entity to travel froma third location toward the first location partly based on theX-ordinate and partly based on the Y-ordinate and partly based on thesecond data indicative of the device-detectable energy signature pathhaving existed between the second entity and the first location andpartly based on the third data indicative of no device-detectable energysignature path having existed between the second entity and the secondlocation (e.g. navigation module 3661 responding to signal detectionmodule 3683 indicating that path 3271 is apparently viable and to signaldetection module 3684 indicating that path 3272 is apparently not viableby routing entity 3201 from a current “third” position 3243 back towardthe “first” location 3241). This can occur, for example, in a context inwhich location 3241 is characterized with the X-ordinate 2231 and theY-ordinate 2232 and in which navigation module 3661 routes entity 3201along any of the available paths 3271, 3272 in a direction of travelthat will cause entity 3201 to draw nearer to the “first” position 3241.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for configuring a device to navigate without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,229,163 (“4D GIS basedvirtual reality for moving target prediction”); U.S. Pat. No. 8,224,508(“Viewing device for aircraft comprising means of displaying the finaldestination and associated display method”); U.S. Pat. No. 8,090,526(“Method for determining the horizontal profile of a flight plancomplying with a prescribed vertical flight profile”); U.S. Pat. No.7,881,864 (“Method and apparatus for utilizing geographic locationinformation”); U.S. Pat. No. 7,865,277 (“Obstacle avoidance system andmethod”); U.S. Pat. No. 7,617,024 (“Automatic heading control system fortiltrotor aircraft and helicopters”); U.S. Pat. No. 7,228,232(“Navigating a UAV with obstacle avoidance algorithms”); U.S. Pat. No.7,127,334 (“System and methods for preventing the unauthorized use ofaircraft”); U.S. Pat. No. 6,892,135 (“Navigation system, method anddevice with automatic next turn page”); U.S. Pat. No. 6,694,228(“Control system for remotely operated vehicles for operational payloademployment”).

FIG. 33 depicts a context in which one or more technologies may beimplemented, a system 33 comprising first and second entities 3301,3302. The first entity 3301 (UAD 1005, e.g.) is mobile and may travelalong path 3370 through a series of positions 3341, 3342, 3343, 3344,3345, 3346, 3347 depending upon which navigation protocol 3361, 3362,3363, 3364 it follows. The second entity may be a mountain or building935 or person 727 or UAD 1005 or other mobile or stationary entity. Ineither case, entity 3301 may (optionally) be configured to detect entity3302 at some positions 3341, 3343 (via respective energy signature paths3371, 3373, e.g.) as it travels. Alternatively or additionally, anentity 3302 that is a device may be configured to detect entity 3301 atsome positions 3341, 3343 (via respective energy signature paths 3371,3373, e.g.) as it travels. When entity 3301 is in some other positions3342, 3346, no such detection is possible because one or moreobstructions 3337, 3338 (buildings or trees, e.g.) prevent the existenceof any device-detectable energy signature path between the first andsecond entities 3301, 3302.

With reference now to FIG. 43, shown is a high-level logic flow 43 of anoperational process. Intensive operation 68 describes obtaining anindication of a first time interval from when a device-detectable energysignature path existed between a first entity and a second entity untila reference time (e.g. estimation module 3771 computing a difference3520 between an initial time 2381 at which entity 3301 was at position3341 until a later time 2382 at which entity 3301 was at position 3342).This can occur, for example, in a context in which a first energysignature path P371 existed between the first and second entities 3301,3302 when entity 3301 was at position 3341; in which entity 3301comprises one or more unmanned aerial devices 1005 traveling southward(along path 3370, e.g.) according to a first navigation protocol 3361;in which no such energy signature path existed between the first andsecond entities 3301, 3302 when entity 3301 was at position 3342 (due toan opaque object or other obstruction 3337 therebetween, e.g.); and inwhich a timer 1141 (aboard entity 3301 or other instance of secondaryunit 1150, e.g.) indicates one or more relevant times 2381-2388 toestimation module 3781. In some contexts, for example, energy signaturepath 3371 may comprise a line of sight (along which light reflected byentity 3302 may travel, e.g.) or some other path (a generally directroute through air 585, e.g.) viable for wireless signal transmissions(in an auditory frequency range 2465 or RF range 2475, e.g.). In othercontexts, the “second” entity 3302 may be operable to transmit adistinctive optical signal 2427 (an authorization code 2964, e.g.) alongenergy signature path 3371.

Extensive operation 73 describes signaling a decision whether or not tochange an aerial navigation protocol of the first entity as an automaticand conditional response to a result of comparing a threshold againstthe indication of the first time interval from when thedevice-detectable energy signature path existed between the first entityand the second entity until the reference time (e.g. flight controlmodule 3652 implementing a decision 3549 to guide entity 3301conditionally according to a new/latter navigation protocol 3362 ifcomparator 3742 indicates that time interval 2342 exceeds anoperator-defined threshold 2332 and otherwise generally not implementingsuch a decision 3549). This can occur, for example, in a real-timeimplementation (in which the “reference” time is nominally the present,e.g.) in which timer 2524 indicates a time interval 2342 from whenentity 3301 was at position 3341 until the present; in which threshold2332 indicates a operator-defined time interval of more than tenseconds; and in which entity 3301 generally would otherwise havecontinued to use a prior/default navigation protocol 3361 by whichentity 3301 would have stayed on a nominally southward path 3370 oftravel). In some contexts, for example, navigation protocol 3362 isconfigured to cause entity 3301 to travel along a nominally northward orother path of travel other than path 3370. Alternatively oradditionally, threshold 2332 may indicate a time interval of less thanten minutes.

In some variants, for example, primary unit 3610 and secondary unit 3750may each reside within “first” entity 3301 or within a “third” entity(near position 3344, e.g.) in wireless communication with the “first”entity 3301. This can occur in a context in which the “third” entity isan unmanned aerial device 803, for example, or a stationary structure2750. In one scenario, timer 1141 begins to run (upward, in somevariants) as entity 3301 travels south from a position 3341 from whichthe “second” entity 3302 was visible. Obstruction 3337 prevents entity3302 from being visible as entity 3301 passes position 3342 but entity3301 continues to follow protocol 3361 because difference 3520 is stillsmaller than threshold 2332 and so decision 3549 is negative. As entity3301 reaches position 3343 (at time 2383, e.g.) anotherdevice-detectable energy signature path 3373 (from entity 3302, e.g.) isobserved and so timer 1141 is reset (to its initial value, e.g.). Flightcontrol module 3652 thus continues to implement protocol 3361 at severalpositions 3344, 3345, 3346 so long as difference 3520 (between time 2383and respective times 2384 and 2385 and 2386, e.g.) remains smaller thanthreshold 2332. But as entity 3301 reaches position 3347 comparator 3742signals that the difference 3520 between times 2383, 2387 became largerthan threshold 2332, in response to which flight control module 3652begins to implement one or more other protocols 3362, 3363 instead. Inrespective variants, for example, flight control module 3652 may selectbetween such other protocols 3362, 3363 in response to one or moreenabling or other criteria 2390-2399 described herein. In some contextssuch a protocol 3363 may be performed pursuant to an implementation ofone or more other flows 15-19, 41-47 described herein, for example.

FIG. 34 depicts a context in which one or more technologies may beimplemented. An image 3484 shows an unmanned aerial device 3401 sittingatop a vehicle of a person using a drive-up automated teller machine(ATM) 3410. In some contexts such images (depicting UAD 3401, e.g.) maybe taken by a camera 3415 of a second UAD 3402 or a stationary camera3417. This and other data 3426 (from sensor 3416, e.g.) may be distilledby a data handling module 3425 aboard UAD 3402 (implementing anevent/condition detection unit 400 or decision modules described herein,e.g.). Alternatively or additionally, such data 3426 may be aggregated(with other data 3481, 3482, 3483 pertaining to positions of entitiesdescribed herein, e.g.) and processed regionally (by one or more anomalydetection modules 3485, e.g.). In some contexts, such distillation mayaffect whether or when subsequent notifications (to ATM 3410, e.g.) orarchiving (to one or more media 3495 in network 3490, e.g.) or otherresponses will occur, as described herein.

With reference now to FIG. 44, shown is a high-level logic flow 44 of anoperational process. Intensive operation 57 describes obtainingphotographic data depicting a first unmanned aerial device (e.g. dataaggregation module 3791 receiving one or more images 2374, 3484 showingan unknown UAD 3401). This can occur, for example, in a context in whichsecondary unit 3750 resides in distillation unit 3480 or network 3490and in which image 3484 was initially captured by a camera 3415 aboardUAD 3402. Alternatively or additionally, the photographic data (image2374, e.g.) depicting UAD 3401 may have been captured initially via oneor more sensors 2560 (camera 3417, e.g.) comprising a stationarystructure (ATM 3410, e.g.).

Intensive operation 65 describes obtaining an indication whether or notthe first unmanned aerial device behaved anomalously (e.g. anomalydetection module 3485 applying a positional criterion 2390 to data 3483indicative of an approximate location 2240 of UAD 3401 to generate anindication 2407 of whether UAD 3401 is in a region that isuse-restricted or off limits). Such a region may comprise a house 2845,parcel 2840 of land, facility (a hospital or bank, e.g.), office 1380 orother room, elevation range, or other (2-dimensional or other) zone 782.In some contexts, for example, such a region or its uses may beexpressed in terms of its converse (a permissible zone of operation oractivity therein, e.g.) or affected by other circumstances (time of dayor presence or absence of personnel, e.g.). In some contexts, a device(UAD 2802, e.g.) may implement one or more use restriction definitions2471-2475 applicable to devices or personnel within a zone 782.Definition 2471 may permit only particular UAD's 701, 801 to performidentified tasks 491-499 within the region. Definition 2472 may forbidany UAD from flying within a given distance 2237 (specified by afacility owner or city ordinance, e.g.) of any mobile entity (animal orcar 602 or other device, e.g.) within the region. Definition 2473 mayrequire continuous movement or flight of any UAD's within the region.Definition 2474 may require any UAD within the region either to identifyitself (by transmitting a, e.g.) or its purpose (by transmitting one ormore task identifiers 4501-4503, e.g.) or to leave within a particulartime interval (1-3 minutes, e.g.). In respective variants, anomalydetection module 3485 may be configured to detect anomalous behavior asany deviation from one or more such use restriction definitions2471-2475 in effect. In some variants, for example, anomaly detectionmodule 3485 may be configured to respond to such deviation bytransmitting trigger 2413.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for distilling indications of anomalous behavior without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,098,142 (“Vehiclemonitoring system”); U.S. Pat. No. 8,041,664 (“Supervisory control bynon-humans”); U.S. Pat. No. 7,983,447 (“Imaging environment recognitiondevice”); U.S. Pat. No. 7,893,960 (“Smart sensors for perimeter andborder security”); U.S. Pat. No. 7,737,878 (“Collision and conflictavoidance system for autonomous unmanned air vehicles (UAVs)”); U.S.Pat. No. 7,598,888 (“Rotary wing aircraft proximity warning system witha geographically based avoidance system”); U.S. Pat. No. 7,346,188(“Motion detection method and device, program and vehicle surveillancesystem”); U.S. Pat. No. 7,280,696 (“Video detection/verificationsystem”); U.S. Pat. No. 7,154,275 (“Method and apparatus for detectingindividuals using electrical field sensors”); U.S. Pat. No. 7,093,294(“System and method for detecting and controlling a drone implanted in anetwork attached device such as a computer”); U.S. Pat. No. 7,027,808(“System and method for monitoring and control of wireless moduleslinked to assets”); U.S. Pat. No. 6,965,816 (“PFN/TRAC system FAAupgrades for accountable remote and robotics control to stop theunauthorized use of aircraft and to improve equipment management andpublic safety in transportation”); U.S. Pat. No. 6,734,799 (“Apparatusand method for responding to the health and fitness of a driver of avehicle”).

Extensive operation 74 describes signaling a decision whether or not totransmit the photographic data depicting the first unmanned aerialdevice as an automatic and conditional response to the indicationwhether or not the first unmanned aerial device behaved anomalously(e.g. data distillation module 3783 transmitting one or more images2374, 3484 indicative of current or recent circumstances near UAD 3402to medium 3495 if trigger 2413 is received and otherwise generally nottransmitting such status-indicative data 1240). This can occur, forexample, in a context in which image data 1241 includes video data orother images 2161-2165, 2371-2377, 3484; in which status-indicative data1240 includes GPS data 1242, timing data 1243, or other data derivedfrom sensor input 3582; in which data aggregation module 3791 andanomaly detection module respectively perform operations 57 and 65; andin which data distillation unit 3480 filters out (by data sampling orother selective extraction, e.g.) a portion of status-indicative data1240 that it receives. In some contexts, for example, distillation unit3480 may reside aboard UAD 3402. Alternatively or additionally,distillation unit 3480 may be configured to pass an alarm or otheranomaly-indicative message 2356 as a real-time response (via a speaker1171 of UAD 3402 or a display 1172 of ATM 3410, e.g.).

Another context in which one or more technologies may be implemented isshown in FIG. 45. A medium 4500 (configured to implement storage ortransmission or display, e.g.) may bear one or more instances of jobrecords 4510; data 4550, 4551, 4552, 4553 (comprising measurements 4511,4512, 4513, 4514 or images or other results 4521, 4522, 4523, 4524,4525, e.g.); triggers 4581, 4582, 4583, 4584; thresholds 4591, 4592,4593, 4594; or components of other media 195, 410, 1200, 2100 describedabove. In some variants, for example, a job record may include one ormore task identifiers 4501, 4502, 4503 configured to identify, inrespective embodiments, any of the other tasks indicated herein to beimplemented in one or more devices.

Another context in which one or more technologies may be implemented isshown in FIG. 46. A mounted camera 4636 (supported by a building orother stationary structure, e.g.) is configured to observe one or moreinstances of a particular person (a recipient 4650 of a delivery, e.g.)or a portion thereof (a hand 4664 or face 4665, e.g.) or a wearabledevice (an earpiece 4661 or wristband 4663, e.g.) or a partial or entirevicinity 4655 (room or other facility, e.g.) of one of these entities.Moreover in some contexts, as further described below, recipient 4650may be a user of one or more of the above-described devices (in vicinity4655, e.g.).

With reference now to flow 47 of FIG. 47 and to other flows 15-19 and38-44 described above, in some variants, one or more intensiveoperations 4711, 4716, 4718 described below may (optionally) beperformed in conjunction with one or more intensive operations 51-55described above. Alternatively or additionally, extensive operation 4793described below may likewise comprise or be performed in conjunctionwith one or more extensive operations 81-85 described above.

Intensive operation 4711 describes configuring the first unmanned aerialdevice to perform a first observation of a particular task in a firstzone and a second unmanned aerial device to perform a second observationof the particular task in a second zone (e.g. task implementation module1138 transmitting a trigger 4582 causing UAD 801 to capture an audio orvideo clip 2151 of a person 726 carrying UAD 701 seeking device 775 inzone 781 and also transmitting a trigger 4583 instructing UAD 802 tocapture an audio or video clip 2152 of the person 726 seeking device 775in zone 782). This can occur, for example, in a context in which one ormore UAD's 701 or people 726 are performing the particular task 499(monitoring person 726 seeking device 775, e.g.) across one or more zoneboundaries 789; in which secondary unit 3750 includes event/conditiondetection unit 400 and media 2100, 4500; in which at least one UAD 801,802 contains or otherwise interacts with secondary unit 3750; in whichsuch UAD's 801, 802 or people 726 have different UAD operatingrestrictions in respective zones 781, 782 (UAD 801 lacking permission tomove or transmit only within zone 782, for example, or UAD 802 lackingpermission to move or transmit only within zone 781); and in whichadequate surveillance of the entire task 499 would otherwise beprohibited (by the owners of the respective zones 781, 782, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for coordinating surveillance among two or more observerswithout undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,180,107 (“Activecoordinated tracking for multi-camera systems”); U.S. Pat. No. 7,947,936(“Apparatus and method for cooperative multi target tracking andinterception”); U.S. Pat. No. 7,739,157 (“Method of tracking the realtime location of shoppers, associates, managers and vendors through acommunication multi-network within a store”); U.S. Pat. No. 7,647,232(“Real-time team coordination system for reconnaissance and surveillancemissions”); U.S. Pat. No. 7,295,106 (“Systems and methods forclassifying objects within a monitored zone using multiple surveillancedevices”); U.S. Pat. No. 6,999,876 (“Modular architecture for rapiddeployment and coordination of emergency event field surveillance”);U.S. Pat. No. 6,963,279 (“System and method for transmittingsurveillance signals from multiple units to a number of points”); U.S.Pat. No. 6,577,976 (“Method for dynamic autocalibration of amulti-sensor tracking system and apparatus incorporating it therein”);U.S. Pat. No. 6,333,718 (“Continuous multi-satellite tracking”); U.S.Pat. No. 6,084,827 (“Dual-head multibeam sonar apparatus and method fortracking objects underwater”); U.S. Pat. No. 6,055,523 (“Method andapparatus for multi-sensor, multi-target tracking using a geneticalgorithm”).

Intensive operation 4716 describes configuring the first unmanned aerialdevice to capture normalcy-indicative data relating to a human subject(e.g. task implementation module 1135 causing, by transmitting anappropriate trigger 4581, a data capture module 1108 to record one ormore scalar measurements 4511-4514 or other data 4550-4553 directly orindirectly indicative of whether or not an item recipient 555, user 226,626 or other human subject meets one or more recognizable criteriaindicative of the human subject being impaired or otherwise abnormal).This can occur, for example, in a context in which a primary unit 3610contains a data capture module 1108 of one secondary unit 1150 andreceives the trigger 4581 from another secondary unit 3750; in whichdata 4551 comprises a video clip of the human subject taking something(a purse, e.g.) previously carried by another and then running away (ata pace greater than 4 miles per hour within 5 seconds of the takingevent, e.g.); and in which primary unit 3610 also implements one or moremedia 4500 of a “first” UAD as described above. See, e.g., FIG. 2 or5-10. In some contexts, such optically detectable events 1414 orconditions may be recognizable (as negatively indicative of normalcy,e.g.) by a corresponding optical condition detection module 1404 or bysecurity personnel remotely viewing such data 4550. Alternatively oradditionally, data 4552 may comprise (1) an infrared image indicatingwarmer-than-normal or cooler-than-normal regions of the human subject'sskin; (2) one or more scalar measurements 4511, 4512 of the subject'sbody temperature, exhaled gas analysis (detecting a ketone concentrationor other indication of intoxication, e.g.), rates (of respiration,speech, movement, or heartbeats, e.g.), or other such biometricparameters. Such events 1415 or conditions may be device-detectable orhumanly recognizable (as negatively indicative of normalcy, e.g.) by acorresponding optical condition detection module 1404, by anotherpattern recognition module 1421, or by a person remotely viewing suchdata 4551-4553 in real time. In some contexts, for example, patternrecognition module 1421 may comprise a comparator 1401 configured togenerate one or more results 4521, 4522 (“normal,” e.g.) of comparingone or more performance or biometric measurements 4511-4513 of a user226, 626 each against one or more corresponding normalcy-indicativethresholds 4591-4593 (maxima, e.g.). Such recognition may, for example,trigger the “first” UAD to obtain additional images or measurements 4514pertaining to the apparent normalcy of the human subject.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for obtaining measurements, comparison results, or othernormalcy-indicative data without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,135,957 (“Access control system based on brainpatterns”); U.S. Pat. No. 8,061,842 (“Method of eye aliveness testingand device for eye aliveness testing”); U.S. Pat. No. 7,809,163 (“Methodfor prohibiting a person with a facial mask to operate an automaticteller machine”); U.S. Pat. No. 7,840,346 (“Real time performancecomparison”); U.S. Pat. No. 7,571,101 (“Quantifying psychological stresslevels using voice patterns”); U.S. Pat. No. 7,825,815 (“Apparatus,systems, and methods for gathering and processing biometric andbiomechanical data”); U.S. Pat. No. 7,733,214 (“System and methods forthe remote measurement of a person's biometric data in a controlledstate by way of synchronized music, video and lyrics”); U.S. Pat. No.8,094,009 (“Health-related signaling via wearable items”); U.S. Pat. No.8,145,199 (“Controlling mobile device functions”); U.S. Pat. No.8,211,035 (“System and method for monitoring health using exhaledbreath”); U.S. Pat. No. 7,477,993 (“Multiple sensing system anddevice”); U.S. Pat. No. 8,172,459 (“Apparatus and method for measuringbiologic parameters”); U.S. Pat. No. 8,108,083 (“Vehicular system whichretrieves hospitality information promoting improvement of user'scurrent energy value based on detected temporal change of biologicalcondition”); U.S. Pat. No. 7,787,663 (“System and method for detectingthermal anomalies”).

Intensive operation 4718 describes causing the first unmanned aerialdevice to undertake a performance observation task of a job thatincludes a performance task and the performance observation task (e.g.task implementation module 1137 transmitting to UAD 501, as the “first”UAD, a task identifier 4501 corresponding to a task description 1251calling for specific status-indicative data 1240 relating to anotherdevice 1010 undertaking to fulfill a performance task description 1252corresponding to task identifier 4502). This can occur, for example, inwhich secondary unit 3750 and media 1200, 4500 reside aboard UAD 501; inwhich the “performance” specified by task description 1252 comprisesdelivering an envelope 551; in which task description 1251 relates toobtaining one or more of image data 1241 (including photograph 553,e.g.), GPS data 1242 (of destination 530, e.g.), or timing data 1243documenting the delivery; and in which such observation and performanceare respectively identified by task identifiers 4501, 4502 of a singlecommon job record 4510. Alternatively or additionally, such taskdescription 1251 and other task descriptions 1252, 1253 may comprise jobdescription or other task-related data 1250 managed and delegated by acommon task implementation module 1137. Other such task identifiers ordescriptions may (optionally) comprise a scalar or other operatingparameter 2126 of one or more triggers 421-423, 2111-2120 transmitted bytask implementation modules 1130-1139, for example, as described herein.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for assigning tasks to respective devices without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 7,945,470 (“Facilitatingperformance of submitted tasks by mobile task performers”); U.S. Pat.No. 8,127,300 (“Hardware based dynamic load balancing of message passinginterface tasks”); U.S. Pat. No. 7,716,667 (“Migrating virtual machinesamong computer systems to balance load caused by virtual machines”);U.S. Pat. No. 8,200,084 (“Encoding for information needed for routingand wavelength assignment in wavelength switched optical networks”);U.S. Pat. No. 8,181,168 (“Memory access assignment for parallelprocessing architectures”); U.S. Pat. No. 7,665,092 (“Method andapparatus for distributed state-based load balancing between taskqueues”); U.S. Pat. No. 8,184,860 (“Image processing device forcontrolling a plurality of tasks”); U.S. Pat. No. 7,996,893(“Determining roles for automated tasks in a role-based access controlenvironment”); U.S. Pat. No. 8,184,860 (“Image processing device forcontrolling a plurality of tasks”).

Extensive operation 4793 describes configuring the first unmanned aerialdevice to transmit a wireless signal indicative of having performed aparticular task and not to store any indication of having performed theparticular task (e.g. task implementation module 1136 transmitting atrigger 2114 to which a component of UAD 1005 responds by transmittingone or more optical or other wireless signals 454 indicative of UAD 1005having completed a particular task 491-499 without any component borneby UAD 1005 storing any indication of the particular task having beenperformed). This can occur, for example, in a context in which volatilememory 395 contains an indication 2108 of such completion that taskimplementation module 1136 includes in wireless signal 454 and in whichtask implementation module 1136 comprises event/condition detection unit400. Alternatively or additionally, task implementation module 1136 maybe configured to generate an indication 2108 of such completion (inresponse to one or more of photographs 553, 554 or GPS data 1242 ortiming data 1243 documenting a completed delivery task, e.g.) forinclusion in wireless signal 454.

With reference now to flow 48 of FIG. 48 and to other flows 15-19,38-44, and 47 described above, in some variants, intensive operation4815 described below may (optionally) be performed in conjunction withone or more intensive operations described above. Alternatively oradditionally, one or more extensive operations 4894, 4897, 4898described below may likewise comprise or be performed in conjunctionwith one or more extensive operations described above.

Intensive operation 4815 describes transmitting a wireless signalindicative of a delivery of a package to a device associated with arecipient of the package, the wireless signal indicating at least one ofthe first unmanned aerial device or the package or a sender of thepackage (e.g. data delivery module 154 transmitting a wireless signal451 indicative of a delivery of a package 2050 into a vicinity of anarticle 1400 associated with a purchaser of the package 2050, thewireless signal 451 indicating at least one of the 1st UAD 1005 or thepackage 2050 or a sender 510 of the package 2050). This can occur, forexample, in a context in which primary unit 3610 resides in the “first”UAD 1005 or in another device 1010 described herein; in which the“vicinity” comprises the room in which article 1400 is situated; inwhich task implementation module 1481 transmits various operatingparameters 2126-2128 (specified by a UAD user 226 or package sender 510,e.g.) relating to such delivery. One such sequence 2121, for example,may (optionally) comprise an alias 823 or other expression 2122facilitating an identification of article 1400. Another such expression2122 may comprise global positioning system (GPS) or other destinationcoordinates 605, 606 (of the article 1400, e.g. or of an alternativedestination to be used if the “first” UAD 1005 cannot locate the article1400, e.g.). Other such parameters may comprise one or more distances2171-2175; directions 2186-2189; protocol identifiers, or other suchindications 2101-2109 described herein.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for specifying how a delivery is to be performed without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,156,542 (“Conditional datadelivery to remote devices”); U.S. Pat. No. 8,112,475 (“Managing datadelivery based on device state”); U.S. Pat. No. 8,090,826 (“Schedulingdata delivery to manage device resources”); U.S. Pat. No. 7,647,230(“Method and apparatus for tracking a special service delivery of a mailitem created by an office worker”); U.S. Pat. No. 7,587,369 (“Trustedand secure techniques, systems and methods for item delivery andexecution”); U.S. Pat. No. 7,401,030 (“Method and system for trackingdisposition status of an item to be delivered within an organization”);U.S. Pat. No. 7,225,983 (“Intelligent parcel monitoring and controllingapparatus and method and terminal for executing real-time parcel pickupand delivery and operation method thereof”); U.S. Pat. No. 7,143,937(“Systems and methods for utilizing a tracking label in an item deliverysystem”); U.S. Pat. No. 6,463,354 (“System and method for automaticnotification of upcoming delivery of mail item”).

Extensive operation 4894 describes signaling a decision whether or notto reserve a space for a passenger vehicle (e.g. resource reservationmodule 1156 transmitting a trigger 2118 that is effective to allocateparking space 648 for the use of car 602). This can occur, for example,in a context in which the trigger 2118 includes an affirmative decision2133 (to reserve parking space 648, e.g.) that has been received from aperson (user 626, e.g.) aboard the passenger vehicle; in which secondaryunit 3750 resides in UAD 601 or in a stationary unit (at station 520,e.g.) operable to communicate with UAD 601 and in which resourcereservation module 1156 maintains one or more records 964 indicatingavailable and unavailable parking spaces (in the same parking lot, e.g.)monitored by UAD 601. In some contexts, moreover, UAD 601 may(optionally) perform operation 4894 by hovering or landing in parkingspace 648 to notify passersby that the space is taken.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for associating a thing or person with another thing or personwithout undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,196,809 (“Systemand method for associating an absorbent article with a user”); U.S. Pat.No. 8,180,827 (“Method and apparatus for associating graphic icon ininternet virtual world with user's experience in real world”); U.S. Pat.No. 8,160,615 (“Method and system for generating associations between auser profile and wireless devices”); U.S. Pat. No. 8,131,745(“Associating user identities with different unique identifiers”); U.S.Pat. No. 8,051,429 (“Method for associating data bearing objects withuser interface objects”); U.S. Pat. No. 8,006,194 (“Associating anobject with a relevant data source”); U.S. Pat. No. 7,979,585 (“Systemand method to associate a private user identity with a public useridentity”); U.S. Pat. No. 7,941,505 (“System and method for associatinga user with a user profile in a computer network environment”); U.S.Pat. No. 7,787,870 (“Method and system for associating a user profile toa caller identifier”).

Extensive operation 4897 describes signaling a decision whether or notto reserve a specific resource by associating the specific resource witha specific device or with a specific person (e.g. resource reservationmodule 157 transmitting one or more triggers 2113, 2120 effective forimplementing or broadcasting an association of a sender 510 or device775 with person 725). This can occur, for example, in a context in whichnetwork 190 comprises one or more systems 4-9 and media 1200, 2100, 4500as described herein; in which trigger 2113 includes one expression 2122for the specific resource (sender 510 or device 775, e.g.) and anotherexpression 2122 for the specific entity (device or person, e.g.) withwhich the specific resource is or will be associated. Alternatively oradditionally, in some implementations, resource reservation module 1157may perform operation 4897 by transmitting an indication 2103 that aspecific resource (a modular data handling unit 2078, e.g.) not bereserved for a specific entity (UAD 201, e.g.) by associating thespecific resource with another specific entity (UAD 202, e.g.). This canoccur, for example, in a context in which the specific resource can onlybe associated with one such entity.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for allocating resources without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,204,770 (“Computer-implemented systems and methods forresource allocation”); U.S. Pat. No. 8,200,583 (“Method and system forleasing or purchasing domain names”); U.S. Pat. No. 8,099,339 (“Systemsand methods for pharmacy inventory management”); U.S. Pat. No. 7,979,309(“Method and system for automating inventory management of consumeritems”); U.S. Pat. No. 7,956,769 (“Method and system forreservation-based parking”); U.S. Pat. No. 7,941,354 (“Method and systemfor lease of assets, such as trailers, storage devices and facilities”);U.S. Pat. No. 7,865,409 (“Vehicle inventory management system andmethod”); U.S. Pat. No. 7,839,526 (“Reservation of secondary printingdevices in a substitute printing system”); U.S. Pat. No. 7,836,186(“Automated adjustment of IP address lease time based on usage”); U.S.Pat. No. 7,797,077 (“System and method for managing vending inventory”);U.S. Pat. No. 7,680,691 (“Inventory management system using RFID”); U.S.Pat. No. 7,636,687 (“Method and system for completing a lease for realproperty in an on-line computing environment”); U.S. Pat. No. 7,636,669(“Recreational outing reservation system”).

Extensive operation 4898 describes responding to an indication of thefirst unmanned aerial device becoming within a proximity of a mobiledevice (e.g. proximity detection module 1153 determining whether UAD1005 has come into a vicinity 4655 of an earpiece 4661, wristband 4663,or other article 1400 wearable by a person). This can occur, forexample, in a context in which such an article 1400 (comprising device775, e.g.) is worn by a person 725 who is moving (toward or away fromUAD 1005, e.g.); in which proximity detection module 1153 resides withinthe (wearable or other mobile) device 775 or within the “first” UAD1005; in which one or more components of such device are thereby able todetect a proximity of the other device; and in which proximity detectionmodule 1153 responds by invoking one or more task implementation modules1130-1139, 1481-1486 described herein.

A first device may “become within” a proximity of a second device by oneor both such devices moving toward the other. Each proximity detectionmodule 1153 may, in some instances, operate by having a sensor as acomponent of a first device that detects the other device becoming closeenough to the sensor to be detected by the sensor, irrespective of whichdevice(s) moved. Alternatively or additionally, some implementations ofproximity detection module 1153 may reside remotely from both devicesand may be configured to determine the devices' mutual proximity fromtheir respective coordinates 605, 606. In some contexts, for example, aproximity of an object may comprise a room (of a patient in a hospital,e.g.) containing the object. In others, a proximity (of target 1360,e.g.) may comprise only an immediate vicinity 1371 (within a fewcentimeters, e.g.) of the object or may comprise an entire surface(desktop 1372, e.g.) on which such an object is positioned.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for computing a difference between locations without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,044,798 (“Passive microwavespeed and intrusion detection system”); U.S. Pat. No. 8,026,850(“Apparatus and method for computing location of a moving beacon usingtime difference of arrival and multi-frequencies”); U.S. Pat. No.7,962,283 (“Deviation-correction system for positioning of movingobjects and motion tracking method thereof”); U.S. Pat. No. 7,778,792(“Systems and methods for location, motion, and contact detection andtracking in a networked audiovisual device”); U.S. Pat. No. 7,775,329(“Method and detection system for monitoring the speed of an elevatorcar”); U.S. Pat. No. 7,671,795 (“Wireless communications device withglobal positioning based on received motion data and method for usetherewith”); U.S. Pat. No. 7,647,049 (“Detection of high velocitymovement in a telecommunication system”); U.S. Pat. No. 7,460,052(“Multiple frequency through-the-wall motion detection and ranging usinga difference-based estimation technique”); U.S. Pat. No. 7,242,462(“Speed detection methods and devices”); U.S. Pat. No. 6,985,206(“Baseball pitch speed measurement and strike zone detection devices”);U.S. Pat. No. 6,400,304 (“Integrated GPS radar speed detection system”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for detecting whether two devices are near one another withoutundue experimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,078,107 (“Automatic networkand device configuration for handheld devices based on bluetooth deviceproximity”); U.S. Pat. No. 8,050,243 (“Method and system for evaluatingproximity to a WLAN for a UMA/GAN compatible electronic device”); U.S.Pat. No. 8,019,283 (“Automatic data encryption and access control basedon Bluetooth device proximity”); U.S. Pat. No. 7,769,984 (“Dual-issuanceof microprocessor instructions using dual dependency matrices”); U.S.Pat. No. 7,574,077 (“Optical imaging device for optical proximitycommunication”); U.S. Pat. No. 7,289,184 (“Liquid crystal panel andequipment comprising said liquid crystal panel”); U.S. Pat. No.7,010,098 (“Ultrasonic proximity detector for a telephone device”); U.S.Pat. No. 6,735,444 (“Method and system for locating a device using alocal wireless link”); U.S. Pat. No. 6,114,950 (“Obstacle proximitywarning device for vehicles”).

With reference now to flow 49 of FIG. 49 and to other flows 15-19,38-44, 47, 48 described above, in some variants, one or more intensiveoperations 4911, 4913, 4917 described below may (optionally) beperformed in conjunction with one or more intensive operations describedabove. Alternatively or additionally, one or more extensive operations4992, 4999 described below may likewise comprise or be performed inconjunction with one or more extensive operations described above.

Intensive operation 4911 describes presenting navigation guidance via adisplay aboard the first unmanned aerial device while a primary motor ofthe first unmanned aerial device is not moving the first unmanned aerialdevice (e.g. triggering interface control module 1111 to outputnavigation guidance 2130 via a touchscreen or other display 1172 borneby UAD 1005 after controller 1085 stops motor 1081). This can occur, forexample, in a context in which UAD 1005 includes a secondary unit 3750that includes one or more media 2110 and in which controller 1085switches motor 1081 off. Alternatively or additionally, taskimplementation module 1131 may perform operation 4911 by displayingguidance 2130 (arrows, words, or other turn-by-turn navigationinstructions for a pedestrian or motor vehicle, e.g.). In some variants,for example, such guidance 2130 may be outputted locally (to a user 226via a speaker 1171 or display 1172, 2072 aboard UAD 1005, e.g.) whileUAD 1005 is stationary (tethered or hovering or landed, e.g.).Alternatively or additionally, in some variants, such taskimplementation modules 1131, 1132 may be disabled selectively by asignal from controller 1085 (a control signal indicating that motor 1081is active, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for providing navigational guidance without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,179,287 (“Method andapparatus for communicating map and route guidance information forvehicle navigation”); U.S. Pat. No. 8,170,798 (“Navigation system andoperation guidance display method for use in this navigation system”);U.S. Pat. No. 8,155,805 (“Flight guidance and navigation display for ahelicopter”); U.S. Pat. No. 7,970,539 (“Method of direction-guidanceusing 3D sound and navigation system using the method”); U.S. Pat. No.7,899,617 (“Navigation system providing route guidance in multi-laneroad according to vehicle lane position”); U.S. Pat. No. 7,881,497(“Vision based navigation and guidance system”); U.S. Pat. No. 7,805,306(“Voice guidance device and navigation device with the same”); U.S. Pat.No. 6,901,330 (“Navigation system, method and device with voiceguidance”); U.S. Pat. No. 6,459,935 (“Integrated filter feed-thru”);U.S. Pat. No. 6,374,182 (“Method and system for providing walkinginstructions with route guidance in a navigation program”).

Intensive operation 4913 describes transmitting navigation guidance viaa speaker of the first unmanned aerial device while a primary motor ofthe first unmanned aerial device is not moving the first unmanned aerialdevice (e.g. task implementation module 1132 triggering interfacecontrol module 1111 to output navigation guidance 2130 via a speaker1171 borne by UAD 1005 after controller 1085 disengages motor 1081 frompropeller 1071). This can occur, for example, in a context in which UAD1005 includes a secondary unit 3750 that includes one or more media 2110and in which controller 1085 permits UAD 1005 to idle (drift or land,e.g.) by disengaging one or more primary motors 1081, 1082 thereof fromone or more props 1071, 1072 to which it/they correspond (by mechanicalcoupling, e.g.). In some variants, for example, such task implementationmodules 1131, 1132 may be enabled (so that it is possible for thetransmission to coincide with the condition recited in operation 4913,e.g.) by a signal from a sensor array 1494 positioned adjacent one ormore props 1071, 1072 (indicating that they are stopped, e.g.).

Intensive operation 4917 describes identifying an operating mode of thefirst unmanned aerial device audibly or visibly while a primary motor ofthe first unmanned aerial device is not moving the first unmanned aerialdevice (e.g. task implementation module 1133 identifying one or moretriggers 2111-2120 or operating parameters 2126-2128 relating to how UAD701 is performing or will perform a current or scheduled task 491-499 sothat a person 726 who is carrying UAD 701 can hear or see suchinformation). This can occur, for example, in a context in which speaker1171 can announce such information audibly (in response to a voice menuaboard UAD 701, e.g.) or in which a display 1172, 2072 aboard UAD 701can present such information visibly, or both. This can occur, forexample, in a context in which the operating mode(s) that currentlyapply to the UAD (silent or not, flight permitted or not, e.g.) can be afunction of which of the proximate zones 781, 782 currently contain UAD701.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for reporting current or scheduled operating parameterswithout undue experimentation or for configuring other decisions anddevices as described herein. See, e.g., U.S. Pat. No. 8,203,426 (“Feedprotocol used to report status and event information in physical accesscontrol system”); U.S. Pat. No. 8,171,318 (“Reporting flash memoryoperating voltages”); U.S. Pat. No. 8,121,083 (“Method and device forreporting request for uplink scheduling or emergency in wirelessnetwork”); U.S. Pat. No. 8,024,138 (“Power supply circuitry, collectionand reporting of power supply parameter information”); U.S. Pat. No.8,014,974 (“System and method for analyzing and reporting machineoperating parameters”); U.S. Pat. No. 7,983,759 (“Advanced patientmanagement for reporting multiple health-related parameters”); U.S. Pat.No. 7,756,822 (“Operational reporting architecture”); U.S. Pat. No.7,245,702 (“Method and apparatus for determining and reporting theoperational status of an integrated services hub”).

Extensive operation 4992 describes causing a modular observation unit tobe lifted and activated within at most about an hour of the modularobservation unit becoming part of the first unmanned aerial device (e.g.an interface control module 1114, motion control module 1158, deviceactivation module 1472, and an engagement structure 2030 of UAD 1005jointly picking up cargo module 2090 and then activating a data handlingunit 2078 thereof). This can occur, for example, in a context in whichengagement structure 2030 (one or more robotic arms 2039, e.g.) comprisea mechanical linkage 2040 between cargo module 2090 and the remainder ofUAD 1005; in which interface control module 1114 transmits one trigger2115 causing motion control module 1158 to engage one or more motors1081, 1082 to rotate props 1071, 1072 so that UAD 1005 takes off; and inwhich interface control module 1114 transmits another trigger 2116causing device activation module 1472 to acquire image data 1241 byactivating a camera 2071 of data handling unit 2078. In some variants,for example, trigger 2116 may be configured to actuate post 2006(sliding it along shaft 2025 rightward, as shown, into recess 2023,e.g.) so that post 2006 engages and supports a modular observation unit(a package 2050 containing a sensor array 1494, e.g.). This can occur ina context in which motion control module 1158 positions UAD 1005 so thata topmost portion of package 2050 extends up into groove 2026, forexample. In other contexts, a user may (optionally) position structure2030 (relative to package 2050, e.g.) or may otherwise facilitatelinkage 2040. Alternatively or additionally, in some variants, themodular observation unit (a camera 2071 or GPS 1063 in cargo module2090, e.g.) may be lifted (by engagement structure 2030, e.g.)responsive to an indication of the modular observation unit becomingpart of the first unmanned aerial device (a control signal activatingengagement structure 2030 or a sensor signal indicating an activation ofengagement structure 2030, e.g.) or to the modular observation unitbeing activated. In some variants, moreover, the modular observationunit may be activated (by device activation module 1472, e.g.)responsive to an indication of the modular observation unit becomingpart of the first unmanned aerial device (a control signal activatingengagement structure 2030 or a sensor signal indicating an activation ofengagement structure 2030, e.g.) or to the modular observation unitbeing lifted. In a context in which UAD 1005 implements UAD 501,moreover, such a user may generate one or more triggers 2111-2120 asdescribed herein (trigger 2116 causing device activation module 1472 toacquire sensor data, e.g.) by pressing a button 561 (positioned on acargo module 2090 of UAD 1005, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for aerial motion control without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 7,962,254 (“Method and system for assisting flight controlof a low-flying aircraft”); U.S. Pat. No. 7,931,238 (“Automatic velocitycontrol system for aircraft”); U.S. Pat. No. 7,837,143 (“Method andapparatus for disabling pilot control of a hijacked aircraft”); U.S.Pat. No. 7,806,371 (“Remote control model aircraft with laser tagshooting action”); U.S. Pat. No. 7,787,998 (“Method and device forassisting the lateral control of an aircraft running on a runway”); U.S.Pat. No. 7,669,805 (“Device for remotely controlling aircraft controlsurfaces”); U.S. Pat. No. 7,617,024 (“Automatic heading control systemfor tiltrotor aircraft and helicopters”); U.S. Pat. No. 7,262,730(“Method and a station for assisting the control of an aircraft”); U.S.Pat. No. 6,991,304 (“Method and device for automatic control of anaircraft deceleration in running phase”); U.S. Pat. No. 6,917,863(“System for assuming and maintaining secure remote control of anaircraft”).

Extensive operation 4999 describes signaling a decision whether or notto configure the first unmanned aerial device to continue observing afirst person responsive to a prior observation of the first person (e.g.task implementation module 1134 responding to a behavioral indication2102 from pattern recognition module 1422 by generating a positive ornegative decision 2132 about whether to transmit a trigger 2117instructing UAD 801 to continue one or more tasks 492, 493 that includeobserving person 727). This can occur, for example, in a context inwhich a portable article 1400 (UAD 701, e.g.) comprising secondary unit3750 is positioned so that it can observe person 727 (sensing his speechor movements, e.g.); in which an initial task 492 comprises UAD 802providing image data 1241 or other sensor data (comprising the priorobservation, e.g.) to pattern recognition module 1422 for analysis; inwhich pattern recognition module 1422 comprises one or more of a gesturedetection module 1402 or a spoken expression detection module 1403 or anoptical condition detection module; and in which a positive behavioralindication 2102 results from one or more recognizable events 1412-1415being detected. In some contexts, task implementation module 1134 may beconfigured so that decision 2132 will generally be negative(contraindicative of monitoring, e.g.) if the behavioral indication 2102is normal (within expected bounds, e.g.), for example, and willotherwise generally be positive. In some variants, moreover, patternrecognition module 1422 may be configured to detect events (a key pressinput detection event 1415, e.g.) relating to person 727 from otherUAD's or systems described herein (a keyboard 1391 or other input 121 ofa stationary primary unit 3610, e.g.). Alternatively or additionally, insome contexts, pattern recognition module 1422 may be configured totransmit a positive or negative behavioral indication 2102 resultingfrom some other event (a timer expiration, e.g.) occurring before any ofsuch recognizable events (recognizable by whichever event/conditiondetection logic 1410 is active, e.g.) are detected.

Alternatively or additionally, task implementation module 1134 may beconfigured to perform operation 4999 by responding to one or moreattribute indications 2101 (relating to identity, shape, preference, orother such static attributes, e.g.) of a subject of observation (an itemrecipient 4650 or other person described herein, e.g.). Taskimplementation module 1134 may thus be configured to implement acontinued observation of such a subject via a “first” UAD 801 inresponse to any combination of (1) one or more indications 2104 that thesubject's face 4665 or clothing 728 resembles that of a particularperson of interest, (2) one or more indications 2105 that the subjecthas spoken or otherwise used particular terminology of interest (athreat or classified program name, e.g.), or (3) one or more indications2106 that the subject has taken a recognizable action of interest (fireda gun or entered an office 1380, e.g.). Such recognizable indications2104-2106 may be based on the “prior observations” from the “first” UAD801, from another UAD 802, from another device, or from some combinationof these. In some contexts, for example, such indications 2104-2106 fromtwo or more such devices may be correlated or otherwise aggregated (byselective retention module 159, e.g.) according to status-indicativedata (image data 1241, GPS data 1242, or timing data 1243 indicative ofperformance, e.g.) from each respective device.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for detecting a particular person or event without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,184,914 (“Method and systemof person identification by facial image”); U.S. Pat. No. 8,170,532(“Method and system for identification using a portable wirelesscommunication device of a person”); U.S. Pat. No. 8,144,881 (“Audio gaincontrol using specific-loudness-based auditory event detection”); U.S.Pat. No. 8,109,891 (“Device and method for detecting an epilepticevent”); U.S. Pat. No. 8,040,245 (“Hand washing monitor for detectingthe entry and identification of a person”); U.S. Pat. No. 8,036,891(“Methods of identification using voice sound analysis”); U.S. Pat. No.7,995,731 (“Tag interrogator and microphone array for identifying aperson speaking in a room”); U.S. Pat. No. 7,774,719 (“System and methodfor conducting online visual identification of a person”); U.S. Pat. No.7,653,697 (“System, method and apparatus for communicating via soundmessages and personal sound identifiers”); U.S. Pat. No. 7,596,248(“Method for identification of person by recognition of a digitalfingerprint”); U.S. Pat. No. 7,596,241 (“System and method for automaticperson counting and detection of specific events”); U.S. Pat. No.7,492,926 (“Method for identifying a person from a detected eye image”).

With reference now to flow 50 of FIG. 50 and to other flows 15-19,38-44, 47-49 described above, in some variants, one or more intensiveoperations 5011, 5016, 5017 described below may (optionally) beperformed in conjunction with one or more intensive operations describedabove. Alternatively or additionally, one or more extensive operations5093, 5094, 5095 described below may likewise comprise or be performedin conjunction with one or more extensive operations described above.

Intensive operation 5011 describes causing another unmanned aerialdevice to capture delivery data relating to the first unmanned aerialdevice (e.g. device activation module 1471 transmitting one or morerequests 373, invitations 374, or other triggers 4584 that result in UAD803 acquiring observations of UAD 801 completing a delivery). Referringto FIG. 8, for example, this can occur in a context in which a trackingcontrol module 149 aboard UAD 803 receives a task description 1252specifying what audio clips 563, photographs 553, 554 or other recordsmay constitute acceptable delivery data 4553 and in which deviceactivation module 1471 resides in UAD 801 (as the “first” UAD, e.g.) orin a stationary control unit 860 in wireless communication with UAD 803.Alternatively or additionally, device activation module 1471 may performoperation 5011 by configuring another UAD (an instance of UAD 1005,e.g.) to indicate an observed result 4523 (a location or other indicatorof incremental success, e.g.) of one or more other tasks 491-499(incorporating a delivery component, e.g.) being undertaken by a “first”UAD described herein.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for programmatic image capture or other event tracking withoutundue experimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,149,288 (“Image capturedevice that records image accordant with predetermined condition andstorage medium that stores program”); U.S. Pat. No. 8,004,563 (“Methodand system for effectively performing event detection using featurestreams of image sequences”); U.S. Pat. No. 7,643,686 (“Multi-tieredimage clustering by event”); U.S. Pat. No. 7,476,796 (“Image controllingapparatus capable of controlling reproduction of image data inaccordance with event”); U.S. Pat. No. 6,721,640 (“Event based aircraftimage and data recording system”); U.S. Pat. No. 6,167,186 (“Videorecording device for retroactively reproducing a video image of anevent, while also recording images in real time”).

Intensive operation 5016 describes configuring the first unmanned aerialdevice not to be equipped with any light sensors (e.g. deviceconfiguration module 1475 transmitting a trigger 2119 that causes arobotic arm 2039 affixed to UAD 1005 to release an optical sensor aboardUAD 1005). This can occur, for example, in a context in which cargomodule 2090 implements an instance of article 1400 that includes acharge-coupled device 1493 or other sensor array 1494 comprising opticalsensors; in which another instance of article 1400 transmits trigger2119 to robotic arm 2039; in which UAD 1005 implements at least one UAD801-3 that is capable of navigating to a healthcare or item recipient4650 or other destination 530 without any need for an onboard camera2071 or CCD 1493; and in which a user can readily discern which cargomodule 2090 (if any) is being carried by UAD 1005. In some contexts, forexample, an inspection of UAD 1005 would not otherwise provide a user(recipient 4650, e.g.) with an adequate assurance of privacy.

Alternatively or additionally, operation 5016 may be performed by aninstance of device configuration module 1475 that manufactures UAD 1005(at a factory, e.g.) as a “blind” device (i.e. lacking light sensors).This can occur, for example, in a context in which “first” UAD 1005implements UAD 801 (of FIG. 8) and in which device configuration module1475 implements non-optical position sensing (sonar, e.g.) or opticalposition sensing via optical sensors not borne by UAD 1005 (in astationary control unit 860 or aboard a second UAD 802, e.g.).

Intensive operation 5017 describes causing a data handling device aboardthe first unmanned aerial device to contain a task schedule indicating afirst future delivery of a first object to a first destination and asecond future delivery of a second object to a second destination (e.g.task implementation module 1134 causing a memory 395 or disk drive 1495aboard the UAD 1005 to contain several tasks 491-494, 1211-1214comprising the first future delivery and the second future delivery).This can occur, for example, in a context in which task 491 associates(by inclusion in a single common table entry 1225, e.g.) a taskidentifier 1221 with one or more of a description of the “first”destination (an immediate vicinity 1371 of target 1360, e.g.) or adescription of the “first” object (an inhaler 2062, e.g.) or otherspecifications 1223 (tracking mode, e.g.) pertaining to the first futuredelivery; in which task 494 associates another task identifier 1221 withone or more of a description of the “second” destination 530 or adescription of the “second” object (a rescued second UAD 202, e.g.) orother specifications 1223 (aborting the delivery if anyone is present,e.g.) pertaining to the second future delivery.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for scheduling deliveries without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,090,826 (“Scheduling data delivery to manage deviceresources”); U.S. Pat. No. 7,929,559 (“Method of scheduling messagedelivery in a wireless communication system”); U.S. Pat. No. 7,516,082(“Scheduling delivery of chemical products based on a predictedestimated time of exhaustion”); U.S. Pat. No. 7,437,305 (“Schedulingdelivery of products via the internet”); U.S. Pat. No. 7,233,907(“Parcel or service delivery with partially scheduled time windows”);U.S. Pat. No. 7,174,305 (“Method and system for scheduling onlinetargeted content delivery”); U.S. Pat. No. 6,985,871 (“Systems andmethods for scheduling reoccurring deliveries and pickups”); U.S. Pat.No. 6,826,534 (“Agent and method for dynamically scheduling publicationin an automated document delivery system”); U.S. Pat. No. 6,238,290(“System and method for scheduled delivery of a software program over acable network”); U.S. Pat. No. 6,009,409 (“System and method forscheduling and controlling delivery of advertising in a communicationsnetwork”).

Extensive operation 5093 describes causing the first unmanned aerialdevice to execute a delivery of a single dose of a therapeutic materialto a human hand within one minute of an image capture of a portion ofthe human hand (e.g. task implementation module 1484 causing UAD 501 tocomplete a delivery of a single syringe 556 directly into a hand 4664 ofa healthcare recipient 4650 or caregiver). This can occur, for examplein a context in which such delivery occurs within a minute before orafter a camera 4636 captures one or more images (photograph 554, e.g.)depicting a palm, finger, or other feature of the hand 4664 distinctiveenough to prove the delivery recipient's identity; in which suchimage(s) also depict the syringe 2061 or other dose clearly enough toprove the delivery occurred; in which the “first” UAD carries at mostone (nominal) dose of the therapeutic material at any given time; inwhich the therapeutic material is highly addictive and expensive; and inwhich an installed dispenser or other device configured to administermore than one dose would be vulnerable to break-ins or other abuse.Alternatively, in some contexts, the only bioactive material borne byUAD 1005 (implementing UAD 501, e.g.) is the single dose 2064 in acapsule 2063.

In some embodiments, a process step occurs “within” a time interval ofan event if the event occurs before or after the process step by anamount of time that does not exceed the time interval. A device or othermodule that is configured to perform an action “within” a time intervalmay include a timer 1141 or other circuitry configured to ensure suchperformance. In fact a module may be “configured to” perform a briefaction (of 1-2 seconds, e.g.) within a long interval (of 1-2 minutes,e.g.), even if the interval is not signaled, in some contexts (in whichthe performance occurs during a portion of the interval in which theprocess step is enabled, e.g.).

In some embodiments, a device is “configured to execute” a task ifspecial-purpose hardware or software aboard the device enables the UADto actually complete the task. Likewise a UAD is “configured to execute”a task if such components aboard the UAD will enable the UAD to completethe task autonomously provided that no overriding instructions (“abort,”e.g.) or other intervening events or conditions (blockages, e.g.)prevent such completion. A component is “aboard” a UAD if it resides inor on the UAD or is mechanically supported by the UAD (hanging from theUAD by a tether or otherwise affixed to the UAD, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for automatic positioning without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,108,091 (“Automatic position-based guide toy vehicleapparatus”); U.S. Pat. No. 8,027,761 (“Local positioning system forautomated lawn mowers”); U.S. Pat. No. 7,869,562 (“Automatic patientpositioning system”); U.S. Pat. No. 7,693,565 (“Method and apparatus forautomatically positioning a structure within a field of view”); U.S.Pat. No. 7,502,684 (“Method and system for the automatic piloting of anaircraft on the approach to an airdrop position”); U.S. Pat. No.6,942,369 (“Device for the automatic adjustment of the position of theheadlights on a motor vehicle”); U.S. Pat. No. 6,931,596 (“Automaticpositioning of display depending upon the viewer's location”).

Extensive operation 5094 describes configuring the first unmanned aerialdevice to execute a delivery of a particular material to a vicinity of aportable device within one minute of an image capture of the vicinity ofthe portable device (e.g. task implementation module 1482 responding toa photographic image 2161 depicting a position 1463 right above a cup1464 of coffee by transmitting a trigger 2112 to one or more dispensers2038 of UAD 1005, which respond by delivering cream or sugar into thecup 1464). This can occur, for example, in a context in which taskimplementation module 1482 previously transmitted a trigger 2111commanding one or more flight control modules 151, 152 to guide UAD 1005approximately to position 1463; in which camera 2071 comprises a cargomodule 2090 carried by a robotic arm 2039 or other support structure2030 of UAD 1005; and in which camera 2071 captures a video clip 2153comprising a succession of images 2161, 2162 depicting a top view of cup1464 via which an optical condition detection module 1404 mayeffectively control the alignment of the one or more dispensers 2038relative to cup 1464. In some contexts, for example, other preparations(verifying a user preference, e.g.) may occur before the delivery iscompleted (during the “one minute,” e.g.). Alternatively oradditionally, in some variants, such an image 2161 (suitable forverifying alignment, e.g.) may be obtained via a charge-coupled device1493 (aboard UAD 1005 or another UAD tasked with observation, e.g.) orvia a stationary-mount surveillance camera 936 (mounted on a building935 or other stationary object, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for delivering an item to a vicinity of a device without undueexperimentation or for configuring other decisions and devices asdescribed herein. See, e.g., U.S. Pat. No. 8,167,786 (“Systems andmethods for delivering a medical implant to an anatomical location in apatient”); U.S. Pat. No. 7,822,463 (“Method for delivering a device to atarget location”); U.S. Pat. No. 7,735,631 (“Mail processing system andmethod of delivering articles to delivery locations therein”); U.S. Pat.No. 7,670,329 (“Systems and methods for delivering drugs to selectedlocations within the body”); U.S. Pat. No. 7,658,156 (“Apparatus andmethod for delivering beneficial agents to subterranean locations”);U.S. Pat. No. 7,361,183 (“Locator and delivery device and method ofuse”); U.S. Pat. No. 6,711,555 (“Method and apparatus for deliveringmail items to non-postal route locations”).

Extensive operation 5095 describes causing the first unmanned aerialdevice to execute a delivery of a particular object to a human recipientcontemporaneously with an image capture of a portion of the humanrecipient (e.g. task implementation module 1483 transmitting one or moretriggers 2110, 2116 that configure UAD 1005 to deliver the object torecipient 4650 within about ten seconds of when a camera 2071, 4636captures an image 2164 of a hand 4664 or face 4665 of the recipient4650). This can occur, for example, in a context in which the objectcomprises a passive radio frequency identification (RFID) chip 1461, anenvelope 551 or other package 2050 (containing an inhaler 2062 or othertherapeutic product 2060, e.g.), a data handling unit 2078 (a memory 395or other medium, e.g.), a battery 2085 or other power source, a wearablearticle (earpiece 4661 or wristband 4663, e.g.), a “second” UAD, orsimilar physical objects. In some variants, for example, such imagecapture occurs in response to one or more triggers from taskimplementation module 1483.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for determining how one or more portions of a person's bodyare positioned without undue experimentation or for configuring otherdecisions and devices as described herein. See, e.g., U.S. Pat. No.7,978,084 (“Body position monitoring system”); U.S. Pat. No. 7,949,089(“Apparatus and method for tracking feature's position in human body”);U.S. Pat. No. 7,934,267 (“Articles of apparel providing enhanced bodyposition feedback”); U.S. Pat. No. 7,916,066 (“Method and apparatus fora body position monitor and fall detector using radar”); U.S. Pat. No.7,889,913 (“Automatic compositing of 3D objects in a still frame orseries of frames”); U.S. Pat. No. 7,630,806 (“System and method fordetecting and protecting pedestrians”); U.S. Pat. No. 7,029,031 (“Methodand device for detecting the position and the posture of a human body”);U.S. Pat. No. 6,692,449 (“Methods and system for assessing limb positionsense during movement”).

With reference now to flow 51 of FIG. 51 and to other flows 15-19,38-44, 47-50 described above, in some variants, one or more intensiveoperations 5112, 5119 described below may (optionally) be performed inconjunction with one or more intensive operations described above.Alternatively or additionally, one or more extensive operations 5195,5196 described below may likewise comprise or be performed inconjunction with one or more extensive operations described above.

Intensive operation 5112 describes determining whether or not anoperator of the first unmanned aerial device has indicated a trackingmode of the first unmanned aerial device (e.g. interface control module1110 determining whether any specifications 1223 provided by a user 226of UAD 1005 contain any indication 2109 of whether or how any ongoing orfuture task 491-499, 1211-1214 assigned to UAD 1005 should be tracked).This can occur, for example, in a context in which user 226 indicatesvia input 391 (a mouse or keyboard 1391, e.g.) a decision 2131 that adefault tracking mode 361 for UAD 1005 (for use in tasks not specifyingan exception, e.g.) should be “none” (not record any aspect of tasksperformed by UAD 1005, e.g.). Alternatively or additionally, suchdecisions 2131 or specifications 1223 may indicate “periodic” tracking(recording image data 1241, GPS data 1242, wind speed, or otherstatus-indicative data 1240 relating to UAD 1005 periodically, e.g.)with operating parameter 2127 specifying the tracking period (how longto wait between successive recording events, e.g.) and operatingparameter 2128 specifying the source of data to be recorded(event/condition detection logic 1410 or camera 2071, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for task performance monitoring without undue experimentationor for configuring other decisions and devices as described herein. See,e.g., U.S. Pat. No. 8,171,474 (“System and method for managing,scheduling, controlling and monitoring execution of jobs by a jobscheduler utilizing a publish/subscription interface”); U.S. Pat. No.8,164,461 (“Monitoring task performance”); U.S. Pat. No. 7,996,658(“Processor system and method for monitoring performance of a selectedtask among a plurality of tasks”); U.S. Pat. No. 7,953,806 (“Taskassignment and progress monitoring in an instant messaging session”);U.S. Pat. No. 7,784,946 (“Virtual microscope system for monitoring theprogress of corneal ablative surgery and associated methods”); U.S. Pat.No. 7,764,179 (“Method of an apparatus for monitoring the processingcycle of a job and instructing workers to perform events or stepsaccording to a standard”); U.S. Pat. No. 7,610,213 (“Apparatus andmethod for monitoring progress of customer generated trouble tickets”);U.S. Pat. No. 7,494,464 (“Monitoring system for monitoring the progressof neurological diseases”); U.S. Pat. No. 7,331,019 (“System and methodfor real-time configurable monitoring and management of task performancesystems”); U.S. Pat. No. 6,669,653 (“Method and apparatus for monitoringthe progress of labor”); U.S. Pat. No. 6,569,690 (“Monitoring system fordetermining progress in a fabrication activity”); U.S. Pat. No.6,034,361 (“System for monitoring the progress of a chemical reaction ina microwave-assisted heating system”); U.S. Pat. No. 6,033,316 (“Golfcourse progress monitor to alleviate slow play”).

Intensive operation 5119 describes overriding a first task beingperformed by the first unmanned aerial device by transmitting a wirelesssignal indicative of a second task to the first unmanned aerial device(e.g. task implementation module 1139 transmitting a wireless signal2192 indicative of a pickup task 1213 and a delivery task 1214 to aninterface control module 142 of a UAD 1005 that is performing alower-priority task 1211). This can occur, for example, in a context inwhich interface control module 142 includes a task scheduler 1220indicating one or more ongoing, contingent, upcoming, or other tasks1211-1214; in which task scheduler 1220 earlier received (from one ormore task implementation modules 1130-1139, e.g.) another signal 2191indicative of the lower-priority task 1211; and in which scalar values1222 control the respective rankings of the scheduled tasks 1211-1214 sothat an intermediate-priority task 1212 (energy replenishment, e.g.)will be performed before “lower-priority” tasks and after“higher-priority” tasks. In other variants, however, task implementationmodule 1139 may be (a) configured to modify the scalar value 1222 oftask 1212 (to indicate a higher priority, e.g.) responsive to anindication that one or more higher priority tasks 1213, 1214 will not becompleted (due to capacity limitations, e.g.) without first executingtask 1212 or (b) configured to be performed contingently (with a highestpriority, but only if a particular condition (running below afuel/charge threshold 4594 or other such conditions set forth in thetask specification 1223, e.g.) is met.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for ranking tasks without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,200,491 (“Method and system for automatically detectingmorphemes in a task classification system using lattices”); U.S. Pat.No. 8,185,536 (“Rank-order service providers based on desired serviceproperties”); U.S. Pat. No. 8,135,708 (“Relevance ranked facetedmetadata search engine”); U.S. Pat. No. 8,095,612 (“Ranking messages inan electronic messaging environment”); U.S. Pat. No. 8,087,019 (“Systemsand methods for performing machine-implemented tasks”); U.S. Pat. No.7,969,922 (“Apparatus and methods for providing configurable taskmanagement of a wireless device”); U.S. Pat. No. 7,945,470(“Facilitating performance of submitted tasks by mobile taskperformers”); U.S. Pat. No. 7,885,222 (“Task scheduler responsive toconnectivity prerequisites”); U.S. Pat. No. 8,127,300 (“Hardware baseddynamic load balancing of message passing interface tasks”); U.S. Pat.No. 7,290,005 (“System for improving the performance of informationretrieval-type tasks by identifying the relations of constituents”).

Extensive operation 5195 describes causing the first unmanned aerialdevice to fly toward a home station in response to an indication of aspecific person moving at least a threshold distance away from the firstunmanned aerial device (e.g. sequence recognition module 1106transmitting a trigger 423 to a controller 1085, 1095 of the “first” UADinstructing the latter to fly home in response to an outcome of protocol418 indicating that one or more device-identifiable people 725 havemoved at least a minimum distance 2174 in a direction generally awayfrom the 1st UAD). This can occur, for example, in a context in which(at least) the navigation of UAD 1005 is locally controlled (viaon-board controller 1085, e.g.); in which controller 1085 has access toprotocol 418 (implemented therein as a software subroutine or inspecial-purpose circuitry, e.g.); in which the “first” UAD comprises ahelicopter 1002 or other UAD 1005 of FIG. 10 (featuring one or moreaspects of UAD's depicted above in systems 4-9, e.g.); and in which oneor more kiosks 250 or other stations 520, 930 are qualifying “homestations” (identified by coordinates 606, a distinctive auditory oroptical signal from a beacon 217 near such station(s), or other suchexpressions 2122 (in trigger 423, e.g.) useable by a flight controlmodule 151, 152.

In one context, sequence recognition module 1106 (implementing oneembodiment of protocol 418, e.g.) has been notified that entityidentification module 144 has detected person 725 being “near” the firstUAD—close enough that facial recognition, proximity sensors 449, orother suitable technologies described herein generate an output 1142identifying person 725 as the “specific person” and explicitly orotherwise indicating a distance 2171 and direction 2186 of initialseparation (in a 2- or 3-dimensional frame of reference, e.g.). Sequencerecognition module 1106 responds to this notification by iterativelydetermining (each 0.1 or 1 second, e.g.) where person 725 is relative toher prior position (indicating her movement distance 2172 and direction2187, e.g.) and by accumulating the movements (as vector-valued orscalar-valued components, e.g.) and comparing a resultant vectormagnitude or other scalar distance 2173 (for at least those iterationsin which person 725 moved generally away from the first UAD, e.g.)against the threshold distance 2174. (It should be noted that device 775would be moving “generally away” from another UAD 701, situated directlyto the south as shown, by moving west-northwest or north oreast-northeast.) In some contexts, sequence recognition module 1106 maybe configured to transmit a heading or otherwise-expressed direction2188 (comprising trigger 423, e.g.) generally toward a (nearest orother) home station 520 relative to UAD 701's current location, wherebyUAD 701 is caused to fly toward home station 520.

Alternatively or additionally, protocol 418 (implemented in a sequencerecognition module 1107 within a controller 1095 remote from a “first”UAD 1005 under its control, e.g.) may make a similar determination of aUAD user 226, 626 (either being the “specific person”) moving at least athreshold distance 2175 (of roughly 1 to 10 meters, within 1 or 2 ordersof magnitude, e.g.) away from the first UAD as a manifestation of suchuser(s) being finished with or otherwise not in need of the first UAD.This can occur, for example, in a context in which “first” UAD 1005 haslanded or started hovering in a locality in response to sequencerecognition module 1107 receiving an indication of such user(s) beingnear the first UAD (from entity identification module 144 or proximitysensor 449, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for estimating a distance or movement (of one person or objectrelative to another, e.g.) without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 7,782,365 (“Enhanced video/still image correlation”); U.S.Pat. No. 8,219,312 (“Determining speed parameters in a geographicarea”); U.S. Pat. No. 8,219,116 (“Wireless base station locationestimation”); U.S. Pat. No. 8,207,869 (“Position estimation fornavigation devices”); U.S. Pat. No. 8,138,976 (“Method for positionestimation using generalized error distributions”); U.S. Pat. No.7,592,945 (“Method of estimating target elevation utilizing radar datafusion”); U.S. Pat. No. 7,532,896 (“Wireless node location mechanismusing antenna pattern diversity to enhance accuracy of locationestimates”); U.S. Pat. No. 8,068,802 (“Estimating the location of awireless terminal based on calibrated signal-strength measurements”);U.S. Pat. No. 7,895,013 (“Estimation of the speed of a mobile device”);U.S. Pat. No. 7,720,554 (“Methods and apparatus for position estimationusing reflected light sources”).

Extensive operation 5196 describes responding to a determination ofwhether or not a received signal expresses a first name of the firstunmanned aerial device and whether or not the received signal expressesa second name of the first unmanned aerial device (e.g. patternrecognition module 1423 transmitting respective results 4524, 4525 ofsearching a sequence 2121 of characters of an incoming signal 2194 forany instance of the “first” UAD name 1425 or any instance of the“second” UAD name 1426). This can occur, for example, in a context inwhich such results 4524, 4525 are each Boolean values (“positive” iffound and otherwise “negative,” e.g.); in which such names 1425, 1426are aliases 822, 823 identifying UAD 802; in which control unit 860includes storage or transmission media 2100, 4500; and in whichinstances of article 1400 comprise control unit 860 and reside innetwork 890. Alternatively or additionally, in some variants, patternrecognition module 1423 may respond to a positive search/comparisonresult (an indication that at least one of the UAD names was found amongin signal 2194, e.g.) by programmatically and conditionally invoking oneor more device activation modules 1471, 1472 or causing a transmissionof one or more triggers 2111-2120 described herein.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for pattern matching without undue experimentation or forconfiguring other decisions and devices as described herein. See, e.g.,U.S. Pat. No. 8,209,278 (“Computer editing system for common textualpatterns in legal documents”); U.S. Pat. No. 8,209,171 (“Methods andapparatus relating to searching of spoken audio data”); U.S. Pat. No.8,171,567 (“Authentication method and system”); U.S. Pat. No. 8,023,695(“Methods for analyzing electronic media including video and audio”);U.S. Pat. No. 7,917,514 (“Visual and multi-dimensional search”); U.S.Pat. No. 8,131,540 (“Method and system for extending keyword searchingto syntactically and semantically annotated data”).

Referring again to the flow embodiments of FIGS. 15 and 47-51, othervariants of data acquisition module 138 may perform operation53—obtaining first data indicating that a first unmanned aerial devicedelivered a first item to a first entity—by asking for, receiving, andrecording (via an interface 390 or other data handling unit 2078 in avicinity 4655 of an item recipient 4650, e.g.) a spoken confirmation 382that the item was received. This can occur, for example, in a context inwhich UAD 1005 includes data handling unit 207; in which an engagementstructure 2030 of UAD 1005 (post 2006 or robotic arm 2039, e.g.)releases cargo module 490 (a cell phone, e.g.) in a vicinity 4655 ofrecipient 4650; and in which data acquisition module 138 triggers thedata handling unit 2078 to ask for and cause a recordation of a spokenconfirmation 382 (as audio clip 563, for example, obtained by conductingan automated telephone call or similar verbal interchange via datahandling unit 2078, e.g.) from recipient 4650. In the variants set forthabove, for example, operation 53 and one or more others of theabove-describe intensive operations may be initiated by processor 365(executing a respective variant of high-level command 484, e.g.) or byinvoking special-purpose circuitry as described above.

Other variants of data delivery module 153 may likewise performoperation 84 of flow 15—transmitting via a free space medium the firstdata to a provider of the first item as an automatic and conditionalresponse to the first data indicating that the first unmanned aerialdevice delivered the first item to the first entity, the first dataindicating at least one of the first item or the first entity or thefirst unmanned aerial device—by transmitting (to a sender 510 of cargomodule 490, e.g.) a wireless signal 2195 (via station 520 through air585, e.g.) containing the recorded spoken confirmation 382 or other dataindicating the delivery within a few minutes after data acquisitionmodule 138 obtains such confirmation. This can occur, for example, in acontext in which one or more systems 5-9 described above implementprimary unit 3610, in which UAD 1005 implements the “first” UAD, and inwhich sender 510 would otherwise be unwilling to send cargo module 490via UAD 1005. In the variants set forth above, for example, operation 84and one or more others of the above-describe extensive operations may beinitiated by processor 365 (executing a respective variant of high-levelcommand 485, e.g.) or by invoking special-purpose circuitry as describedabove.

Referring again to the flow variants of FIGS. 16 and 47-51, othervariants of coordinate communication module 136 may perform operation51—obtaining first position data from a first entity, by a secondentity, the first entity being a first unmanned aerial device—byreceiving an address 562 from UAD 501 indicating the position of sender510). This can occur, for example, in a context in which UAD 501implements UAD 1005 as described above; in which sender 510 is or hasthe “first” resource (a data handling unit 2078 or other package 2050 orproduct 2060 described herein, e.g.); and in which such resource(s) maybe allocated as described herein (purchased or temporarily reserved bythe “second” entity, e.g.). This can occur, for example, in a context inwhich the second entity (recipient 4650, e.g.) is remote from thelocation specified by the first position data (not within the same roomor facility, e.g.). In the variants set forth above, for example,operation 51 and one or more others of the above-describe intensiveoperations may be initiated by processor 365 (executing a respectivevariant of high-level command 484, e.g.) or by invoking special-purposecircuitry as described above.

Other variants of resource reservation module 156 may likewise performoperation 83 of flow 16—signaling a decision whether or not to allocatea first resource to the second entity after the first position datapasses from the first unmanned aerial device to the second entity, thefirst resource being associated with the first position data—bytransmitting an indication 2107 that a request 373 for such a resourcereservation 376 has been declined. This can occur in a context in whichthe first resource is offline or otherwise unavailable, for example, orin which no device is authorized to grant a reservation of the firstresource. In some contexts, for example, resource reservation module 156may be configured to manage other resources within a defined zone 781 orof a particular type (products 2060, e.g.). Alternatively oradditionally, in some variants, resource reservation module 156 may beconfigured to provide (automatically and conditionally, e.g.) one ormore signals other than whether or not to allocate the first resource(“stand by while I contact an authorized agent for you,” e.g.). In thevariants set forth above, for example, operation 83 and one or moreothers of the above-describe extensive operations may be initiated byprocessor 365 (executing a respective variant of high-level command 485,e.g.) or by invoking special-purpose circuitry as described above.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for associating a user or a device with another user oranother device without undue experimentation or for configuring otherdecisions and devices as described herein. See, e.g., U.S. Pat. No.8,023,485 (“Method, system and device for realizing user identityassociation”); U.S. Pat. No. 7,979,585 (“System and method to associatea private user identity with a public user identity”); U.S. Pat. No.7,970,660 (“Identifying associations between items andemail-address-based user communities”); U.S. Pat. No. 7,941,505 (“Systemand method for associating a user with a user profile in a computernetwork environment”); U.S. Pat. No. 7,894,812 (“Automatic over-the-airupdating of a preferred roaming list (PRL) in a multi-mode device, basedon an account association between the device and a wireless local areanetwork (WLAN) access point”); U.S. Pat. No. 7,743,099 (“Associatingmultiple visibility profiles with a user of real-time communicationsystem”); U.S. Pat. No. 7,716,378 (“System and method to associate aprivate user identity with a public user identity”); U.S. Pat. No.7,703,691 (“Multiple device and/or user association”); U.S. Pat. No.7,627,577 (“System and method for maintaining an association between adistribution device and a shared end user characteristic”); U.S. Pat.No. 6,473,824 (“Dynamic association of input/output device withapplication programs”).

Referring again to the flow variants of FIGS. 17 and 47-51, othervariants of interface control module 141 may perform operation52—causing a first unmanned aerial device to guide a first individual toa first destination—by signaling via UAD 1005 a direction 2189 of one ormore waypoints 642, 742 relative to a current position of the “first”individual along a path to the first destination. In the context of FIG.6, for example, an interface control module 141 may be configured toperform operation 52 by prompting UAD 601 (implementing UAD 1005, e.g.)to signal (via a wireless communication linkage 694, e.g.) a directionof a waypoint 642 to guide a driver (by causing user interface 660 todisplay an upward arrow to user 626, e.g.) along a path 643 to the firstdestination (parking space 648, e.g.). Another implementation ofinterface control module 141 may be configured to perform operation 52by configuring UAD 701 (implementing UAD 1005, e.g.) to signal adirection of a waypoint 742 to guide a pedestrian (via a speaker 1171 ordisplay 1172 aboard UAD 1005, e.g.) along a path 743 (to “first”destination 530, e.g.). In relation to these variants and others setforth above, operation 52 and one or more others of the above-describeintensive operations may (optionally) be initiated by processor 365(executing a respective variant of high-level command 484, e.g.) or byinvoking special-purpose circuitry as described above.

Other variants of flight control module 152 may likewise performoperation 85 of flow 17—causing the first unmanned aerial device to flyto a second destination as an automatic and conditional response to anindication of the first individual arriving at the first destination—bycausing UAD 1005 to fly to the “second” destination after, andresponsive to, the “first” individual apparently arriving at a parkingspace 648 or other “first” destination 530). This can occur, forexample, in a context in which the “second” destination relates to atask 491-499 to be performed next; in which one or more otherconditions, events, or indications 2101-2109 described herein also occur(detected by event/condition detection logic 1410 or signaled by one ormore triggers 2111-2120, e.g.); and in which flight control module 152implements such flight by triggering a task implementation module 1485aboard UAD 1005 to activate one or more motors 1081-1083 aboard UAD 1005controlling one or more props 1071-1073 aboard UAD 1005. In the variantsset forth above, for example, operation 85 and one or more others of theabove-describe extensive operations may be initiated by processor 365(executing a respective variant of high-level command 485, e.g.) or byinvoking special-purpose circuitry as described above.

Referring again to the flow variants of FIGS. 18 and 47-51, othervariants of enlistment module 133 may perform operation 54—indicating afirst unmanned aerial device participating in a first task—by notifyingdevice operators (e.g. users 226, 626) or other persons 725, 726 that a“first” task 491-499 (or component task thereof) as described herein hasbeen begun by or accepted on behalf of “first” UAD 1005. This can occur,for example, in a context in which network 190 contains UAD 1005 and inwhich primary unit 3610 contains interface device 310 andevent/condition detection unit 400. In the variants set forth above, forexample, operation 54 and one or more others of the above-describeintensive operations may be initiated by processor 365 (executing arespective variant of high-level command 484, e.g.) or by invokingspecial-purpose circuitry as described above.

Other variants of control unit 860 may likewise perform operation 82 offlow 18—signaling a decision whether or not to cause the first unmannedaerial device to recognize an alias identifying the first unmannedaerial device as an automatic and conditional response to an indicationof the first unmanned aerial device participating in the first task, thealias being different than a primary digital identifier of the firstunmanned aerial device—by configuring a name recognition module 147 ofcontrol unit 860 to recognize and use the primary identifier 821 of UAD1005 (instead of an alias, e.g.) partly based on an indication of UAD1005 participating in a “first” task 491-499 described herein and partlybased on an indication that UAD 1005 has not accepted any aliases 822,823. This can occur, for example, in a context in which the decision isnegative (not to cause UAD 1005 to recognize any aliases, e.g.); inwhich control unit 860 makes the negative decision in response to UAD1005 not responding to a configuration request within a prescribedinterval; in which UAD 1005 implements UAD 802; in which control unit860 implements primary unit 3610; and in which control unit 860addresses UAD 1005 during such task(s) using primary identifier 821.Alternatively, in some contexts, UAD 1005 may generate such a negativedecision. In the variants set forth above, for example, operation 82 andone or more others of the above-describe extensive operations may beinitiated by processor 365 (executing a respective variant of high-levelcommand 485, e.g.) or by invoking special-purpose circuitry as describedabove.

Referring again to the flow variants of FIGS. 19 and 47-51, othervariants of tracking control module 977 may perform operation55—obtaining a tracking mode of a delivery task of a first unmannedaerial device—by receiving a device-executable command sequence 2125implementing a user-defined mode 363 of tracking one or more deliverytasks 491, 494 performed or being performed by UAD 1005. This can occur,for example, in a context in which UAD 1005 implements interface device310 and media 1200, 2100; in which processor 365 executesdevice-executable command sequence 2125 (e.g. capturing one or more ofimage data 1241, GPS data 1242, or timing data 1243) periodically or inresponse to a trigger 2111-2120 described herein. Alternatively oradditionally, a one or more user-specified expressions 2122 (expressingrules that incorporate OR, AND, or other logical operators, e.g.) mayidentify one or more device-detectable indications 2101-2109 that enableor disable such tracking (respectively as a prerequisite or exception,e.g.). In the variants set forth above, for example, operation 55 andone or more others of the above-describe intensive operations may beinitiated by processor 365 (executing a respective variant of high-levelcommand 484, e.g.) or by invoking special-purpose circuitry as describedabove.

Other variants of selective retention module 158 may likewise performoperation 81 of flow 19—signaling a decision whether or not to omit arecord of the first unmanned aerial device completing the delivery taskof the first unmanned aerial device as an automatic and conditionalresponse to the tracking mode of the delivery task of the first unmannedaerial device—by transmitting a selection of records 961-964 that arerecognized by one or more gesture detection modules 1402, spokenexpression detection modules 1403, optical condition detection modules1404, or other pattern recognition modules 1421-1423 configured todetect one or more events 1412-1414 (a gesture or word or otherexpression of acknowledgment from a delivery recipient 4650, e.g.)specified by the tracking mode (and detectable as visual or auditoryphenomena in one or more records 961-964, e.g.). This can occur, forexample, in a context in which a sender 510 of an item delivered decidesto specify what kind(s) of expression (saying “take my picture,” e.g.)should trigger tracking; in which the sender 510 expresses suchdecision(s) as the tracking mode 982; and in which the first UAD 1005would not otherwise perform any tracking upon completion of one or moredelivery tasks 491, 494. In the variants set forth above, for example,operation 81 and one or more others of the above-describe extensiveoperations may be initiated by processor 365 (executing a respectivevariant of high-level command 485, e.g.) or by invoking special-purposecircuitry as described above.

Referring again to flows 15-19 and to variants thereof described withreference to FIGS. 47-51, in some implementations, each of these flowsmay (optionally) be performed entirely within a “first” unmanned aerialdevice (in UAD 1005, e.g.) or within another device described herein. Insome implementations, for example, each of these flows may be performedentirely within a vehicle as described herein (car 602, e.g.) or withina single handheld device (e.g. a cell phone or handheld UAD 202, 701) orin a wearable article (an earpiece 4661, wristband 4663, or similarchip-containing device, for example, or an article of clothing 728having such a device affixed thereto). Alternatively or additionally,the first unmanned aerial device may include the second aerial device(as a cargo module 2090 thereof, e.g.). In some embodiments, moreover,each of these flows may be performed by a network 1090 of devices orotherwise shared among two or more such devices 1010.

Referring again to the flow variants of FIGS. 38 & 47-51, operation64—obtaining a descriptor of a first entity operating a first unmannedaerial device—may also be performed by pattern recognition module 3639.Such performance may include generating a null or default name 2241(“guest” or “anonymous,” e.g.) initially in response to proximitydetection module 3721 detecting a “first” UAD 1005 about which nooperatorship information has yet been acquired. Alternatively oradditionally, pattern recognition module 3639 may perform operation 64by reading a barcode 2271 or other device-readable name 2242 from anexternal label 2275 affixed to UAD 1005. Alternatively or additionally,such a descriptor 2254 may comprise a passive RFID tag 2267 or otherdevice-readable data-handling medium 2200 comprising descriptors 2250 asdescribed herein.

Also in such variants, operation 67—obtaining an operatorshipcriterion—may be performed by pattern recognition module 3637. Suchperformance may include accepting a criterion 2394 (implemented in aninstance of code 2463 executable by processor 3565, e.g.) that issatisfied for any descriptor that is defined and not blank. This canoccur, for example, in a context in which stationary structure 2750includes primary unit 3610; in which pattern recognition module 3637 isinvoked whenever operation 64 occurs or whenever UAD 1005 crosses aboundary (a perimeter of parcel 2840 or entryway threshold, e.g.); andin which primary unit 3610 is configured to control a second entity asdescribed herein.

Also in such variants, operation 72—signaling a decision whether or notto impede the first unmanned aerial device entering a particular regionas an automatic and conditional result of applying the operatorshipcriterion to the descriptor of the first entity operating the firstunmanned aerial device—may be performed by decision module 3673. Suchperformance may include manifesting a decision 3543 to cause a secondentity (an actuator 2710 or UAD 803, e.g.) to allow the “first” UAD 1005to approach something (by entering a room or vicinity 785, e.g.) if anydescriptors 2250 of UAD 1005 satisfy one or more operatorship criteria2392-2396 obtained in operation 67 and in which such a second entityotherwise does nothing (passively impeding the “first” UAD 1005 enteringthe region, e.g.). This can occur, for example, in a context in which aperson 725 (an administrator or owner of a region or such a secondentity, e.g.) selects or otherwise defines such operatorship criteria2392-2396. Alternatively or additionally, decision module 3673 mayperform operation 72 by transmitting a message 2357 (“exit eastwardimmediately” or a similar warning, e.g.) to UAD 1005 or by disabling UAD1005 (by targeting UAD 1005 with an adhesive 2681, bullet or othermissile 2682, incendiary, entanglement line 2683 extended by a grapplinghook or similar weight 2684, or other such disablement device 2690,e.g.).

Referring again to the flow variants of FIGS. 39 & 47-51, operation63—detecting a first unmanned aerial device being within a vicinity of aportal—may also be performed by proximity detection module 3722. Suchperformance may include a secondary unit 3750 on or in a building 945,2745 having a portal (aperture 2741, e.g.) detecting that UAD 1005 iswithin a proximity of the portal. Alternatively or additionally, aninstance of detection module 3722 aboard UAD 1005 may likewise performoperation 63 by determining that UAD 1005 is within a proximity (a lineof sight or predetermined distance 2239, e.g.) of such a portal.

Also in such variants, operation 61—obtaining an indication of anidentity of the first unmanned aerial device—may be performed by signaldetection module 3682 receiving a model 352 or operatorship identifier2866 that indicates an identity of UAD 1005. This can occur, forexample, in a context in which primary unit 3610 includes interfacedevice 310 and interacts with secondary unit 3750 and in which interfacedevice 310 controls or comprises UAD 1005. In some variants, forexample, UAD 1005 may implement UAD 2801. Alternatively or additionally,in some contexts, operation 61 may be performed before or concurrentlywith operation 63.

Also in such variants, operation 75—signaling a decision whether or notto allow an actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal—may be performed by task implementation module3752. Such performance may, in some variants, include triggering anopening of door 2742 (so that it will not obstruct aperture 2741 and) sothat UAD 1005 can enter aperture 2741. This can occur, for example, in acontext in which secondary unit 3750 is mounted on building 2745 or nearaperture 2741 and configured so that proximity detection module 3722 andsignal detection module 3722 are both operably coupled with taskimplementation module 3752. Alternatively or additionally, secondaryunit 3750 may (optionally) be configured to communicate with UAD 1005such as by confirming the identity (a street address 2235, e.g.) ofbuilding 2745 or by transmitting an authorization 2358 to enter.

Referring again to the flow variants of FIGS. 40 & 47-51, operation66—obtaining first data including optical data from a vicinity of areference surface in contact with a first unmanned aerial device—mayalso be performed by a camera 2541 or other sensors 2560. In somecontexts, such performance may include camera 2541 capturing image 2373(as the optical data that is a component of the “first” data 2321, e.g.)while aboard a “first” UAD 1005 resting upon a landing station 950 orother suitable mooring site (platform 2725, e.g.). This can occur, forexample, in a context in which UAD 1005 includes (an instance of)detection unit 2500 and medium 2300; in which part of the “first” data2321 is obtained via a data handling unit 2078, 3550 aboard “first” UAD1005; in which another part of the “first” data 2321 is obtained via astationary sensor 3552, 3115 (of stationary structure 2750, e.g.); inwhich stationary structure 2750 comprises building 955; and in whichdetection unit 2500 can operate while UAD 1005 rests upon the referencesurface. In some contexts, UAD 1005 may implement a UAD 3005 havingelectrical contacts 3141 (on respective arms 3151 thereof, e.g.) bywhich a primary energy source 1022 of UAD 3005 (battery 2085, e.g.) canrecharge. Alternatively or additionally, the reference surface(s) may bepart of a structure (comprising a combination of base 3010 and wall3020, e.g.) that includes a stationary power source (an outlet 3019 orinductive charging coil 3122, e.g.). In some contexts, for example, abody 3190 of UAD 3005 may contain a coil (not shown) that UAD 3005 canalign with inductive charging coil 3122 for contactless charging of UAD3005 (implementing UAD 1005, e.g.).

Also in such variants, operation 77—signaling a decision as an automaticand conditional response to the application of a first recognitioncriterion to the optical data from the vicinity of the reference surfacein contact with the first unmanned aerial device whether or not to causethe first unmanned aerial device to be disengaged from the referencesurface—may be performed by decision module 3676. In some contexts, suchperformance may include generating such a decision 3547 to cause the“first” UAD 1005 to remain in contact with the reference surface if noanomalous event 1412-1414 is detected. This can occur, for example, in acontext in which one or more of gesture detection module 1402, spokenexpression module 1403, or optical condition detection module 1404 areconfigured to disable decision module 3676 (operably coupled by a wireor other signal path therebetween, e.g.) from generating such a decision3547 to maintain contact (in response to an anomalous event 1412-1414,e.g.) and in which UAD 1005 is configured to perform a surveillance task3094 (passing between stations 520, 930 or traversing a patrol route2878, e.g.) in response to an anomalous event 1412-1414 or condition(detected by event/condition detection logic 1410, e.g.) during aninterval 2341 that is expected to be uneventful (at night or on aweekend, e.g.). Alternatively or additionally, decision module 3676 maybe configured to cause UAD 1005 to begin such a surveillance task inresponse to an expiration of a countdown timer 2523 initiated with atimer value 2311 provided by a pseudorandom number generator 3570). Thiscan occur, for example, in a context in which the surveillance behaviorof UAD 1005 might otherwise be easy for an adversary to monitor,characterize, predict, and circumvent.

Also in such variants, operation 78—signaling a decision as an automaticand conditional response to the application of the first recognitioncriterion to the optical data from the vicinity of the reference surfacewhether or not to cause the first unmanned aerial device to obtainsecond data with the first unmanned aerial device disengaged from thereference surface—may be performed by task implementation module 3751.In some contexts, such performance may include obtaining additional data(the “second” data 2322, e.g.) via the “first” UAD 1005 in the samemanner as the “first” data 2321 was obtained. This can occur, forexample, in a context in which UAD 1005 is configured to include acamera 2541 or other sensors 2560 and in which task implementationmodule 3751 performs operation 78 as a consequence of the samecircumstance (result 2451 or decision 3547, e.g.) that caused orresulted from operation 77. In other contexts, however, taskimplementation module 3751 may be configured not to obtain or retain the“second” data 2322 unless one or more additional criteria 2398, 2399 aremet. In some variants, for example, task implementation module 3751 maybe configured to signal a decision 3540 not to configure UAD 1005 tocapture any “second” data 2322 unless a predetermined criterion 2398 ismet (an indication 2403 of UAD 1005 having received one or more triggers2111-2119 described herein, e.g.). Alternatively or additionally, insome variants, task implementation module 3751 may be configured tosignal a decision 3540 not to configure UAD 1005 to retain “second” data2322 unless another predetermined criterion 2399 is met (an indication2404 of one or more particular tasks 491-499 having been performed,e.g.).

Referring again to the flow variants of FIGS. 41 & 47-51, operation59—obtaining operator input from an operator of a first unmanned aerialdevice as an earlier input component—may also be performed by dataaggregation module 3792. This can occur, for example, in a context inwhich UAD 1005 is the “first” UAD, in which operator interface 3712receives thresholds 2331, pattern matching criteria 2397, or other suchoperating parameters 2126-2128 as the earlier input component (a gestureor other input 3583, e.g.) from operator 729 and in which a patternrecognition module 3638 (of event/condition detection logic 1410, e.g.)distills such input 3583 (as a Boolean value 2312 indicating whether ornot an anomaly 2315 is recognized, e.g.) from raw data 2326 (audio orvideo data, e.g.).

Also in such variants, operation 56—obtaining environmental sensor inputfrom a vicinity of the first unmanned aerial device as a later inputcomponent—may be performed by microphones 2552 or other sensors 2560 ina proximity 3155 of the “first” UAD 1005. This can occur, for example,in a context in which the resulting environmental sensor input 3585includes audio data 2323 within which a recognizable pattern 3591(signifying a gunshot, footstep, fire alarm, human voice, or other suchdevice-detectable phenomenon 2354, e.g.) can be found (by patternrecognition module 3630, e.g.). In some places at some times (within ajewelry store at night, e.g.), the apparent occurrence of such phenomenawarrants that the UAD be launched without any (further) operatorinvolvement. Alternatively or additionally, pattern 3591 may require oneor more other specific sensor inputs 3581 (indications of abnormalenvironmental conditions in a vicinity of UAD 1005 from another sensor2560 that performs operation 56, e.g.).

Likewise in such variants, operation 71—signaling a decision withoutregard to any other operator input whether or not to launch the firstunmanned aerial device partly based on the operator input from theoperator of the first unmanned aerial device obtained as the earlierinput component and partly based on the environmental sensor input fromthe vicinity of the first unmanned aerial device obtained as the laterinput component—may be performed by decision module 3672. Suchperformance may include transmitting an affirmative decision 3544 tolaunch the “first” UAD 1005 if and when pattern recognition module 3630detects a phenomenon 2354 (inferred from sensor data, e.g.), forexample, and otherwise generally not transmitting such decision 3544. Insome variants, moreover, UAD 1005 may be configured to investigate thepremises (a building or parcel 2840 of land or patrol route 2878, e.g.)and transmit other sensor data 2327 (images 2161-2165, e.g.) therefromas a programmatic and conditional response to such decision 3544.

Referring again to the flow variants of FIGS. 42 & 47-51, operation58—obtaining first data including an X-ordinate of a first location anda Y-ordinate of the first location indicating a first entity moving fromthe first location to a second location—may also be performed bylocation detection module 3641 generating or receiving position data3483 that signals position 3343 and an indication 2406 of entity 3301moving downward). This can occur, for example, in a context in whichposition 3343 is the “first” location; in which the “first” entity 3301comprises UAD 1005 or another mobile device 1010 described herein; inwhich the position data 3483 includes an instance of X-ordinate 2231(horizontal offset, e.g.) and Y-ordinate 2232 (altitude, e.g.); in whichindication 2406 signals a particular location (position 3346, e.g.) orheading or general direction of travel (downward, e.g.); and in whichone or more media 2200, 2400 reside in primary unit 3610.

Also in such variants, operation 60—obtaining second data indicative ofa device-detectable energy signature path having existed between asecond entity and the first location—may be performed by patternrecognition module 3633 selectively and automatically recognizing one ormore distinctive attributes (a sequence 2121 or other device-detectablepattern 3592, 3593 of frequency or shape components, e.g.) reflected ortransmitted by an entity 3302 (comprising a UAD 803 or tower 2730,e.g.). This can occur, for example, in a context in which entity 3301travels along a path 3370 via position 3343 and position 3345 and inwhich entity 3301 includes a lower-frequency sensor 3551 and ahigher-frequency sensor 3553 of which at least one can detect an audiblesignal 2421, visible shape, or other distinctive pattern 3593 (alongpath 3373, e.g.) at the “first” location (position 3343, e.g.) thatwould not be detectable at the “second” location due to asignal-blocking obstruction 3338 (a bridge, e.g.) between entity 3302and the “second” location (position 3345, e.g.). In some variants, forexample, the lower-frequency sensor 3551 (an auditory or vibrationsensor, e.g.) may have a nominal frequency range 2435 that is entirelylower than a nominal frequency range 2445 of the higher-frequency sensor3553 such that the nominal maximum threshold 2432 of the former is lessthan half of the nominal minimum threshold 2441 of the latter.Alternatively or additionally, data handling unit 3550 may reside withinentity 3301 or in a stationary structure 2750 (tower 2730, e.g.) nearby.

Also in such variants, operation 62—obtaining third data indicative ofno device-detectable energy signature path having existed between thesecond entity and the second location—may be performed by patternrecognition module 3636 determining that a distinctive visible or otherpattern 3593 was apparently not received when entity 3301 was at the“second” location at position 3345. This can occur in a context in whichan obstruction 3338 blocks a view of entity 3302, for example, such thatno device-detectable energy signature path apparently existed betweenthe entity 3302 and the “second” location.

Also in such variants, operation 76—causing the first entity to travelfrom a third location toward the first location partly based on theX-ordinate and partly based on the Y-ordinate and partly based on thesecond data indicative of the device-detectable energy signature pathhaving existed between the second entity and the first location andpartly based on the third data indicative of no device-detectable energysignature path having existed between the second entity and the secondlocation—may be performed by flight control module 3653 causing entity3301 (implementing UAD 1005, e.g.) to travel from a vicinity of position3347 back up (toward position 3341, e.g.) partly based on the “second”and “third” data respectively indicating that “first” entity 3301 coulddetect “second” entity from the “first” location but not from the“second” location. This can occur in a context in which primary unit3610 resides in entity 3301, for example, or in stationary structure2750.

Referring again to the flow variants of FIGS. 43 & 47-51, operation68—obtaining an indication of a first time interval from when adevice-detectable energy signature path existed between a first entityand a second entity until a reference time—may also be performed by acountdown timer 2521 given an initial positive value 2313 thateffectively defines how long “first” entity 3301 can remain in positions3342, 3346 that are apparently not observable (from the vantage of“second” entity 3302, e.g.) without switching navigation protocols. Thiscan occur, for example, in a context in which “first” entity 3301comprises (an instance of) primary unit 3610 and medium 2300; in whichentity 3301 implements a dirigible 1003 or other unmanned aerial device1005; and in which an initial navigation protocol 3531 of entity 3301comprises being controlled by an interface device 310 (held by aparticular user 226, e.g.).

Also in such variants, operation 73—signaling a decision whether or notto change an aerial navigation protocol of the first entity as anautomatic and conditional response to a result of comparing a thresholdagainst the indication of the first time interval from when thedevice-detectable energy signature path existed between the first entityand the second entity until the reference time—may be performed bynavigation module 3662. Such performance may include keeping “first”entity 3301 on protocol 3531 as an automatic and conditional response tocountdown timer 2521 remaining positive. Such performance may likewiseinclude implementing a decision 3548 to reset countdown timer 2521 (toinitial value 2313, e.g.) as a conditional response to adevice-detectable energy signature path 3371 being detected beforecountdown timer 2521 reaches zero. Alternatively or additionally, suchdecision 3548 may (optionally) result in protocol 3532 (autopilot, e.g.)or protocol 3533 (control by an operator 729 via data handling unit3550, e.g.) being implemented as an automatic and conditional responseto navigation module 3662 detecting a device-detectable energy signaturepath (between the first and second entities 3301, 3302, e.g.) beforecountdown timer 2521 reaches zero.

Referring again to the flow variants of FIGS. 44 & 47-51, operation57—obtaining photographic data depicting a first unmanned aerialdevice—may also be performed by signal detection module 3685. Suchperformance may include receiving a wireless signal 2428 containing oneor more images 2375 of UAD 1005 (from a charge-coupled device 1493 orcamera 2918, e.g.). This can occur, for example, in a context in whichprimary unit 3610 is configured to receive such signals via a wirelesslinkage 3694 from an article 1400 that includes storage or transmissionmedia 2300, 2400 (a server in network 3690 operably coupled to a tower2730, e.g.). In some contexts, for example, such an article 1400 mayinclude or otherwise interact with camera 2918. Alternatively oradditionally, such photographic data may include a result 2453 (“notfound,” e.g.) of data distillation module 3781 implementing a patternrecognition protocol upon such images (trying to recognize one or morebarcodes 2271, 2961 or other shape pattern occurrences therein, e.g.).

Also in such variants, operation 65—obtaining an indication whether ornot the first unmanned aerial device behaved anomalously—may beperformed by pattern recognition module 3634. Such performance mayinclude generating an indication 2408 whether or not UAD 1005 apparentlytransmitted any data outside a specified frequency range 2435 whilewithin zone 781. This can occur, for example, in a context in which anoperator 729 of UAD 1005 has provided an assurance or has been notifiedof a requirement that UAD 1005 will only transmit within range 2435while within zone 781 and in which use of other frequency ranges 2445 byUAD 1005 may interfere with other operations within zone 781 or maysignal that UAD 1005 is untrustworthy. Alternatively or additionally, insome variants of pattern recognition module 3634, one or more suchindications 2408 may signal whether UAD 1005 has apparently compliedwith one or more other use restriction definitions 2471-2475 applicableto UAD 1005.

Alternatively or additionally, in some contexts, a data distillationmodule 3784 may be configured to perform operation 65 by selectivelygenerating a result 2452 of comparing one or more tasks 491-499apparently being performed by UAD 1005 against a task list 2463 (of zeroor more tasks) that the first unmanned aerial device normally orpermissibly performs as the indication whether or not the first unmannedaerial device behaved anomalously. Alternatively or additionally, datadistillation module 3784 may be configured to condition such result 2452upon whether an identifier 543 of UAD 1005 (implementing UAD 501, e.g.)appears in an entity list 2464 (of zero or more entities) identifyingany entities that are normally or permissibly present or performing suchtask(s) within a specific zone 781 (on a premises or within a vicinityof destination 530, e.g.).

Also in such variants, operation 74—signaling a decision whether or notto transmit the photographic data depicting the first unmanned aerialdevice as an automatic and conditional response to the indicationwhether or not the first unmanned aerial device behaved anomalously—maybe performed by data distillation module 3782. Such performance mayinclude discarding one or more images 2375 of UAD 1005 at least partlybased on an indication 2408 (from pattern recognition module 3634 ordata distillation module 3784, e.g.) that UAD 1005 apparently compliedwith any applicable requirements of use restriction definitions2471-2475 pertaining to UAD 1005 within zone 781. In some contexts, forexample, data distillation module 3782 may perform operation 74 bytransmitting anomaly-indicative images 2376 at a higher sampling rate(more than 50%, e.g.) than a nominal sampling rate (of less than 50%,e.g.) of normalcy-indicative images 2377. This can occur, for example,in a context in which pattern recognition module 3634 sometimes fails todetect latent anomalies 2315 (an instance of UAD 1005 causing an injuryor participating in an identity theft or other crime, e.g.) among images2375 initially designated as normalcy-indicative images 2377 and inwhich such erroneously-designated normalcy-indicative images 2377 may beused (by a computer programmer, e.g.) in refining pattern recognitionmodule 3634. Alternatively or additionally, data distillation module3782 may be configured to condition such a decision 3672 (whether or notto transmit the photographic data, e.g.) upon whether one or morepattern recognition modules 3635 have identified the UAD 1005.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof, limited to patentablesubject matter under 35 U.S.C. 101.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof, limited to patentablesubject matter under 35 U.S.C. 101. In one embodiment, several portionsof the subject matter described herein may be implemented viaApplication Specific Integrated Circuits (ASICs), Field ProgrammableGate Arrays (FPGAs), digital signal processors (DSPs), or otherintegrated formats. However, those skilled in the art will recognizethat some aspects of the embodiments disclosed herein, in whole or inpart, can be equivalently implemented in integrated circuits, as one ormore computer programs running on one or more computers (e.g., as one ormore programs running on one or more computer systems), as one or moreprograms running on one or more processors (e.g., as one or moreprograms running on one or more microprocessors), as firmware, or asvirtually any combination thereof, and that designing the circuitryand/or writing the code for the software and or firmware would be wellwithin the skill of one of skill in the art in light of this disclosure.In addition, those skilled in the art will appreciate that themechanisms of the subject matter described herein are capable of beingdistributed as a program product in a variety of forms, and that anillustrative embodiment of the subject matter described herein appliesregardless of the particular type of signal bearing medium used toactually carry out the distribution. Examples of a signal bearing mediuminclude, but are not limited to, the following: a recordable type mediumsuch as a floppy disk, a hard disk drive, a Compact Disc (CD), a DigitalVideo Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.).

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

In some instances, one or more components may be referred to herein as“configured to,” “configurable to,” “operable/operative to,”“adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Thoseskilled in the art will recognize that “configured to” can generallyencompass active-state components and/or inactive-state componentsand/or standby-state components, unless context requires otherwise.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B” in respective included configurations.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory).

A sale of a system or method may likewise occur in a territory even ifcomponents of the system or method are located and/or used outside theterritory. Further, implementation of at least part of a system forperforming a method in one territory does not preclude use of the systemin another territory.

With respect to the numbered clauses and claims expressed below, thoseskilled in the art will appreciate that recited operations therein maygenerally be performed in any order. Also, although various operationalflows are presented in a sequence(s), it should be understood that thevarious operations may be performed in other orders than those which areillustrated, or may be performed concurrently. Examples of suchalternate orderings may include overlapping, interleaved, interrupted,reordered, incremental, preparatory, supplemental, simultaneous,reverse, or other variant orderings, unless context dictates otherwise.Furthermore, terms like “responsive to,” “related to,” or otherpast-tense adjectives are generally not intended to exclude suchvariants, unless context dictates otherwise. Also in the numberedclauses below, specific combinations of aspects and embodiments arearticulated in a shorthand form such that (1) according to respectiveembodiments, for each instance in which a “component” or other suchidentifiers appear to be introduced (with “a” or “an,” e.g.) more thanonce in a given chain of clauses, such designations may either identifythe same entity or distinct entities; and (2) what might be called“dependent” clauses below may or may not incorporate, in respectiveembodiments, the features of “independent” clauses to which they referor other features described above.

Clauses

1. A system comprising:

one or more articles of manufacture including

circuitry for obtaining a descriptor of a first entity operating a firstunmanned aerial device;

circuitry for obtaining an operatorship criterion; and

circuitry for signaling a decision whether or not to impede the firstunmanned aerial device entering a particular region as an automatic andconditional result of applying the operatorship criterion to thedescriptor of the first entity operating the first unmanned aerialdevice.

2. The system of CLAUSE 1 in which the circuitry for detecting a firstunmanned aerial device being within a vicinity of a portal comprises:

a proximity sensor configured to detect whether the first unmannedaerial device is within the vicinity of the portal, the vicinity being adetection range of the proximity sensor.

3. The system of CLAUSE 1 in which the circuitry for detecting a firstunmanned aerial device being within a vicinity of a portal comprises:

a radio frequency transceiver configured to detect whether the firstunmanned aerial device is within the vicinity of the portal, thevicinity being a detection range of the radio frequency transceiver.

4. The system of any of the above SYSTEM CLAUSES in which the circuitryfor signaling a decision whether or not to allow an actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal comprises:

circuitry for positioning the actuator partly based on the indication ofthe identity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal,the actuator comprising a door.

5. The system of any of the above SYSTEM CLAUSES in which the circuitryfor signaling a decision whether or not to allow an actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal comprises:

circuitry for positioning the actuator partly based on the indication ofthe identity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal,the actuator comprising a window.

6. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture further comprise:

circuitry for configuring a second unmanned aerial device to perform afirst observation of the first unmanned aerial device in a first zoneand a third unmanned aerial device to perform a second observation ofthe first unmanned aerial device in a second zone, the portal comprisinga boundary between the first zone and the second zone.

7. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a handheld device, including the circuitry for detecting the firstunmanned aerial device being within the vicinity of the portal andincluding the circuitry for obtaining the indication of the identity ofthe first unmanned aerial device and including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal.

8. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a wearable device, including the circuitry for detecting the firstunmanned aerial device being within the vicinity of the portal andincluding the circuitry for obtaining the indication of the identity ofthe first unmanned aerial device and including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal.

9. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture further comprise:

a vehicle having one or more wheels, the vehicle configured to supportthe circuitry for detecting the first unmanned aerial device beingwithin the vicinity of the portal and configured to support thecircuitry for obtaining the indication of the identity of the firstunmanned aerial device and configured to support the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal.

10. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including one or more propellers andincluding the circuitry for detecting the first unmanned aerial devicebeing within the vicinity of the portal and including the circuitry forobtaining the indication of the identity of the first unmanned aerialdevice and including the circuitry for signaling the decision whether ornot to allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal.

11. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for detectingthe first unmanned aerial device being within the vicinity of the portaland including the circuitry for obtaining the indication of the identityof the first unmanned aerial device and including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal.

12. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal.

13. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for configuring the second unmanned aerial device to capturenormalcy-indicative data relating to a human subject.

14. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for causing the second unmanned aerial device to undertake aperformance observation task of a job that includes a performance taskand the performance observation task.

15. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for configuring the second unmanned aerial device to transmita wireless signal indicative of having performed a particular task andnot to store any indication of having performed the particular task.

16. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for transmitting a wireless signal indicative of adelivery of a package to a device associated with a recipient of thepackage, the wireless signal indicating at least one of the secondunmanned aerial device or the package or a sender of the package.

17. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for signaling a decision whether or not to reserve a space fora passenger vehicle.

18. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture further comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for signaling a decision whether or not to reserve a specificresource by associating the specific resource with a specific device orwith a specific person.

19. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for responding to an indication of the secondunmanned aerial device becoming within a proximity of the first unmannedaerial device.

20. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for presenting navigation guidance via a displayaboard the second unmanned aerial device while a primary motor of thesecond unmanned aerial device is not moving the second unmanned aerialdevice.

21. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for transmitting navigation guidance via a speakerof the second unmanned aerial device while a primary motor of the secondunmanned aerial device is not moving the second unmanned aerial device.

22. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for identifying an operating mode of the secondunmanned aerial device audibly or visibly while a primary motor of thesecond unmanned aerial device is not moving the second unmanned aerialdevice.

23. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for causing a modular observation unit to be liftedand activated within at most about an hour of the modular observationunit becoming part of the second unmanned aerial device.

24. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for signaling a decision whether or not to configure thesecond unmanned aerial device to continue observing a first personresponsive to a prior observation of the first person.

25. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for causing a third unmanned aerial device to capture deliverydata relating to the second unmanned aerial device.

26. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for configuring the second unmanned aerial device not to beequipped with any light sensors.

27. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for causing a data handling device aboard the second unmannedaerial device to contain a task schedule indicating a first futuredelivery of a first object to a first destination and a second futuredelivery of a second object to a second destination.

28. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for causing the second unmanned aerial device to execute adelivery of a single dose of a therapeutic material to a human handwithin one minute of an image capture of a portion of the human hand.

29. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for causing the second unmanned aerial device toexecute a delivery of a particular object to a human recipientcontemporaneously with an image capture of a portion of the humanrecipient.

30. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for determining whether or not an operator of the secondunmanned aerial device has indicated a tracking mode of the secondunmanned aerial device.

31. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for overriding a first task being performed by the secondunmanned aerial device by transmitting a wireless signal indicative of asecond task to the second unmanned aerial device.

32. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and

circuitry for causing the second unmanned aerial device to fly toward ahome station in response to an indication of a specific person moving atleast a threshold distance away from the second unmanned aerial device.

33. The system of any of the above SYSTEM CLAUSES in which the one ormore articles of manufacture comprise:

a second unmanned aerial device including the circuitry for signalingthe decision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for responding to a determination of whether or nota received signal expresses a first name of the second unmanned aerialdevice and whether or not the received signal expresses a second name ofthe second unmanned aerial device.

All of the patents and other publications referred to above (notincluding websites) are incorporated herein by referencegenerally—including those identified in relation to particular newapplications of existing techniques—to the extent not inconsistentherewith. While various system, method, article of manufacture, or otherembodiments or aspects have been disclosed above, also, othercombinations of embodiments or aspects will be apparent to those skilledin the art in view of the above disclosure. The various embodiments andaspects disclosed above are for purposes of illustration and are notintended to be limiting, with the true scope and spirit being indicatedin the final claim set that follows.

1. A system comprising: one or more articles of manufacture includingcircuitry for detecting a first unmanned aerial device being within avicinity of a portal; circuitry for obtaining an indication of anidentity of the first unmanned aerial device; and circuitry forsignaling a decision whether or not to allow an actuator to obstruct theportal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal.
 2. The system of claim 1in which the circuitry for detecting a first unmanned aerial devicebeing within a vicinity of a portal comprises: a proximity sensorconfigured to detect whether the first unmanned aerial device is withinthe vicinity of the portal, the vicinity being a detection range of theproximity sensor. 3-6. (canceled)
 7. The system of claim 1 in which theone or more articles of manufacture comprise: a handheld device,including the circuitry for detecting the first unmanned aerial devicebeing within the vicinity of the portal and including the circuitry forobtaining the indication of the identity of the first unmanned aerialdevice and including the circuitry for signaling the decision whether ornot to allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal.
 8. The system of claim 1 in which the one ormore articles of manufacture comprise: a wearable device, including thecircuitry for detecting the first unmanned aerial device being withinthe vicinity of the portal and including the circuitry for obtaining theindication of the identity of the first unmanned aerial device andincluding the circuitry for signaling the decision whether or not toallow the actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal.
 9. (canceled)
 10. The system of claim 1 in which the one or morearticles of manufacture comprise: a second unmanned aerial deviceincluding one or more propellers and including the circuitry fordetecting the first unmanned aerial device being within the vicinity ofthe portal and including the circuitry for obtaining the indication ofthe identity of the first unmanned aerial device and including thecircuitry for signaling the decision whether or not to allow theactuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal.11-12. (canceled)
 13. The system of claim 1 in which the one or morearticles of manufacture comprise: a second unmanned aerial deviceincluding the circuitry for signaling the decision whether or not toallow the actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal; and circuitry for configuring the second unmanned aerial deviceto capture normalcy-indicative data relating to a human subject.
 14. Thesystem of claim 1 in which the one or more articles of manufacturecomprise: a second unmanned aerial device including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal; and circuitry forcausing the second unmanned aerial device to undertake a performanceobservation task of a job that includes a performance task and theperformance observation task.
 15. The system of claim 1 in which the oneor more articles of manufacture comprise: a second unmanned aerialdevice including the circuitry for signaling the decision whether or notto allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal; and circuitry for configuring the secondunmanned aerial device to transmit a wireless signal indicative ofhaving performed a particular task and not to store any indication ofhaving performed the particular task.
 16. The system of claim 1 in whichthe one or more articles of manufacture comprise: a second unmannedaerial device including the circuitry for signaling the decision whetheror not to allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal, the second unmanned aerial device includingcircuitry for transmitting a wireless signal indicative of a delivery ofa package to a device associated with a recipient of the package, thewireless signal indicating at least one of the second unmanned aerialdevice or the package or a sender of the package.
 17. The system ofclaim 1 in which the one or more articles of manufacture comprise: asecond unmanned aerial device including the circuitry for signaling thedecision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal; and circuitry for signaling adecision whether or not to reserve a space for a passenger vehicle. 18.(canceled)
 19. The system of claim 1 in which the one or more articlesof manufacture comprise: a second unmanned aerial device including thecircuitry for signaling the decision whether or not to allow theactuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal,the second unmanned aerial device including circuitry for responding toan indication of the second unmanned aerial device becoming within aproximity of the first unmanned aerial device.
 20. The system of claim 1in which the one or more articles of manufacture comprise: a secondunmanned aerial device including the circuitry for signaling thedecision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for presenting navigation guidance via a displayaboard the second unmanned aerial device while a primary motor of thesecond unmanned aerial device is not moving the second unmanned aerialdevice.
 21. The system of claim 1 in which the one or more articles ofmanufacture comprise: a second unmanned aerial device including thecircuitry for signaling the decision whether or not to allow theactuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal,the second unmanned aerial device including circuitry for transmittingnavigation guidance via a speaker of the second unmanned aerial devicewhile a primary motor of the second unmanned aerial device is not movingthe second unmanned aerial device.
 22. The system of claim 1 in whichthe one or more articles of manufacture comprise: a second unmannedaerial device including the circuitry for signaling the decision whetheror not to allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal, the second unmanned aerial device includingcircuitry for identifying an operating mode of the second unmannedaerial device audibly or visibly while a primary motor of the secondunmanned aerial device is not moving the second unmanned aerial device.23. The system of claim 1 in which the one or more articles ofmanufacture comprise: a second unmanned aerial device including thecircuitry for signaling the decision whether or not to allow theactuator to obstruct the portal partly based on the indication of theidentity of the first unmanned aerial device and partly based on thefirst unmanned aerial device being within the vicinity of the portal,the second unmanned aerial device including circuitry for causing amodular observation unit to be lifted and activated within at most aboutan hour of the modular observation unit becoming part of the secondunmanned aerial device.
 24. The system of claim 1 in which the one ormore articles of manufacture comprise: a second unmanned aerial deviceincluding the circuitry for signaling the decision whether or not toallow the actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal; and circuitry for signaling a decision whether or not toconfigure the second unmanned aerial device to continue observing afirst person responsive to a prior observation of the first person. 25.The system of claim 1 in which the one or more articles of manufacturecomprise: a second unmanned aerial device including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal; and circuitry forcausing a third unmanned aerial device to capture delivery data relatingto the second unmanned aerial device.
 26. The system of claim 1 in whichthe one or more articles of manufacture comprise: a second unmannedaerial device including the circuitry for signaling the decision whetheror not to allow the actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal; and circuitry for configuring the secondunmanned aerial device not to be equipped with any light sensors. 27.The system of claim 1 in which the one or more articles of manufacturecomprise: a second unmanned aerial device including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal; and circuitry forcausing a data handling device aboard the second unmanned aerial deviceto contain a task schedule indicating a first future delivery of a firstobject to a first destination and a second future delivery of a secondobject to a second destination.
 28. (canceled)
 29. The system of claim 1in which the one or more articles of manufacture comprise: a secondunmanned aerial device including the circuitry for signaling thedecision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal, the second unmanned aerial deviceincluding circuitry for causing the second unmanned aerial device toexecute a delivery of a particular object to a human recipientcontemporaneously with an image capture of a portion of the humanrecipient.
 30. (canceled)
 31. The system of claim 1 in which the one ormore articles of manufacture comprise: a second unmanned aerial deviceincluding the circuitry for signaling the decision whether or not toallow the actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal; and circuitry for overriding a first task being performed by thesecond unmanned aerial device by transmitting a wireless signalindicative of a second task to the second unmanned aerial device. 32.The system of claim 1 in which the one or more articles of manufacturecomprise: a second unmanned aerial device including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal; and circuitry forcausing the second unmanned aerial device to fly toward a home stationin response to an indication of a specific person moving at least athreshold distance away from the second unmanned aerial device.
 33. Thesystem of claim 1 in which the one or more articles of manufacturecomprise: a second unmanned aerial device including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal, the second unmannedaerial device including circuitry for responding to a determination ofwhether or not a received signal expresses a first name of the secondunmanned aerial device and whether or not the received signal expressesa second name of the second unmanned aerial device.
 34. A systemcomprising: one or more articles of manufacture including means fordetecting a first unmanned aerial device being within a vicinity of aportal; means for obtaining an indication of an identity of the firstunmanned aerial device; and means for signaling a decision whether ornot to allow an actuator to obstruct the portal partly based on theindication of the identity of the first unmanned aerial device andpartly based on the first unmanned aerial device being within thevicinity of the portal. 35-53. (canceled)
 54. The system of claim 34 inwhich the one or more articles of manufacture comprise: a secondunmanned aerial device including the means for signaling the decisionwhether or not to allow the actuator to obstruct the portal partly basedon the indication of the identity of the first unmanned aerial deviceand partly based on the first unmanned aerial device being within thevicinity of the portal, the second unmanned aerial device includingmeans for identifying an operating mode of the second unmanned aerialdevice audibly or visibly while a primary motor of the second unmannedaerial device is not moving the second unmanned aerial device. 55-65.(canceled)
 66. A method comprising: detecting a first unmanned aerialdevice being within a vicinity of a portal; obtaining an indication ofan identity of the first unmanned aerial device; and invoking circuitryconfigured for signaling a decision whether or not to allow an actuatorto obstruct the portal partly based on the indication of the identity ofthe first unmanned aerial device and partly based on the first unmannedaerial device being within the vicinity of the portal.
 67. The method ofclaim 66 further comprising: configuring a second unmanned aerial deviceto perform a first observation of the first unmanned aerial device in afirst zone and a third unmanned aerial device to perform a secondobservation of the first unmanned aerial device in a second zone, theportal comprising a boundary between the first zone and the second zone.68-69. (canceled)
 70. An article of manufacture comprising: one or morephysical media bearing a device-detectable outcome indicating anoccurrence of detecting a first unmanned aerial device being within avicinity of a portal; obtaining an indication of an identity of thefirst unmanned aerial device; and signaling a decision whether or not toallow an actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal.
 71. The article of manufacture of claim 70 in which a portion ofthe one or more physical media comprises: the actuator manifesting thedecision whether or not to allow the actuator to obstruct the portalpartly based on the indication of the identity of the first unmannedaerial device and partly based on the first unmanned aerial device beingwithin the vicinity of the portal.
 72. The system of claim 1 in whichthe one or more articles of manufacture comprise: a second unmannedaerial device including one or more propellers and including thecircuitry for detecting the first unmanned aerial device being withinthe vicinity of the portal and including the circuitry for obtaining theindication of the identity of the first unmanned aerial device andincluding the circuitry for signaling the decision whether or not toallow the actuator to obstruct the portal partly based on the indicationof the identity of the first unmanned aerial device and partly based onthe first unmanned aerial device being within the vicinity of theportal, the second unmanned aerial device including circuitry forresponding to an indication of the second unmanned aerial devicebecoming within a proximity of the first unmanned aerial device, thesecond unmanned aerial device including circuitry for presentingnavigation guidance via a display aboard the second unmanned aerialdevice while a primary motor of the second unmanned aerial device is notmoving the second unmanned aerial device, the second unmanned aerialdevice including circuitry for causing a modular observation unit to belifted and activated within at most about an hour of the modularobservation unit becoming part of the second unmanned aerial device, thesecond unmanned aerial device including circuitry for responding to adetermination of whether or not a received signal expresses a first nameof the second unmanned aerial device and whether or not the receivedsignal expresses a second name of the second unmanned aerial device;circuitry for configuring the second unmanned aerial device to transmita wireless signal indicative of having performed a particular task andnot to store any indication of having performed the particular task;circuitry for causing a third unmanned aerial device to capture deliverydata relating to the second unmanned aerial device; circuitry forsignaling a decision whether or not to configure the second unmannedaerial device to continue observing a first person responsive to a priorobservation of the first person; and circuitry for causing the secondunmanned aerial device to fly toward a home station in response to anindication of the first person moving at least a threshold distance awayfrom the second unmanned aerial device.
 73. The system of claim 1 inwhich the one or more articles of manufacture comprise: a secondunmanned aerial device including the circuitry for detecting the firstunmanned aerial device being within the vicinity of the portal andincluding the circuitry for obtaining the indication of the identity ofthe first unmanned aerial device and including the circuitry forsignaling the decision whether or not to allow the actuator to obstructthe portal partly based on the indication of the identity of the firstunmanned aerial device and partly based on the first unmanned aerialdevice being within the vicinity of the portal, the second unmannedaerial device including circuitry for responding to an indication of thesecond unmanned aerial device becoming within a proximity of the firstunmanned aerial device, the second unmanned aerial device includingcircuitry for transmitting navigation guidance via a speaker of thesecond unmanned aerial device while a primary motor of the secondunmanned aerial device is not moving the second unmanned aerial device,the second unmanned aerial device including circuitry for causing amodular observation unit to be lifted and activated within at most aboutan hour of the modular observation unit becoming part of the secondunmanned aerial device; circuitry for configuring the second unmannedaerial device to capture normalcy-indicative data relating to the humanrecipient; circuitry for configuring the second unmanned aerial devicenot to be equipped with any light sensors; circuitry for causing thesecond unmanned aerial device to execute a delivery of a single dose ofa therapeutic material to a human hand within one minute of an imagecapture of a portion of the human hand; circuitry for overriding a firsttask being performed by the second unmanned aerial device bytransmitting a wireless signal indicative of a second task to the secondunmanned aerial device; and circuitry for causing the second unmannedaerial device to undertake a performance observation task of a job thatincludes a performance task and the performance observation task.